Hi,
I came across the bug #4444 <http://sourceforge.net/p/phpmyadmin/bugs/4444/>
related to export feature for queries.
I'm not sure how exactly this feature is supposed to behave if we are
exporting rows with some but not all columns and also in case we have
aliases and even when we have join queries.
Assume we have tables:
actor (actor_id, first_name, last_name, city_id) with actor_id as primary
key.
address (address_id, adress, city_id, city_id, district, postal_code,
phone) with address_id as primary key and phone have not null unique
constraints.
1. when we select some but not all columns ex,
Select address_id, address from address:
when exported few of the rows, it have create table statement for table
'address' with all the original columns not just these two. and data from
just these two columns in the Insert statements. so here when the same
exported file, we wish to import back will not work as phone have unique
constraint and we are not inserting the phone values.
Also If user is seeing just two of the columns in the table structure at
screen so they might be doing export thinking that it will be exporting the
same structure as on the screen.
2. When we have aliases in column names:
ex: select actor_id, first_name as fname from actor;
So when we export few of the resultant rows, should the create table
statement have a column name first_name or fname ?. As I think of it, It
should be fname, if user have in mind that he is exporting the structure of
the table he is looking at screen.
3. When we have alias in table names:
The name of the table in create statement should be alias name or original
table name?
4. When we have JOIN queries with more than one tables:
ex:
SELECT * FROM (SELECT actor_id FROM actor as e INNER JOIN address as g on
e.actor_id = g.city_id) as t1
Currently if we try to export some rows from the above query, it export
nothing it goes on edit sql screen.
Please share your thoughts.
Thanks and Regards
- Smita
Hi Edward,
Is there any provision for refreshing the Console at the bottom when user
selects a particular database from the Navi panel; similar to the option to
refresh the Navi panel?
I need this so that we can show the 'Bookmarks' link when the phpMyAdmin
configuration has been set up dynamically (without changing config.inc.php).
--
Ashutosh Dhundhara
Hi,
I was just wondering that do we really need Travis CI builds for the
weblate translation changes as it does not affect test cases.
So why not just ignore builds for those commits and avoid wastage of
resources and keep them available for PR?
As weblate changes are so often it is just an overhead on Travis and
Scrutinizer causing delays for other PR's and commits unnecessarily.
To skip a build on Travis CI & Scrutinizer CI we can add "[ci skip]" or
"[skip ci]" in the commit message (see [1] & [2]). Is it possible to do so?
[1]: http://docs.travis-ci.com/user/how-to-skip-a-build/
[2]:
https://scrutinizer-ci.com/docs/guides/skipping_a_build_via_commit_message
--
Regards,
Chirayu Chiripal
phpMyAdmin Intern - Google Summer of Code 2014
https://chirayuchiripal.wordpress.com/
Hi,
Today, while connecting to my pMA (on master), I did a mistake in my user
name and pressed enter (without a password). Then I was connected and could
only see "information_schema", but not send queries in it.
I tried other user names and as I have no password, I can connect.
Is it the desired behaviour please? Mustn't I have a connection error?
I'll create a ticket if this is not right.
Thanks,
Hugues.
Hi,
I was starting to work on RFE #1123
<https://sourceforge.net/p/phpmyadmin/feature-requests/1123/> (Zeroconf PMA
tables support).
Is it something like enabling/disabling the PMA configuration storage
feature through UI with default table names?
Also, automatically create these tables when user has enabled this feature
through UI?
--
Ashutosh Dhundhara
I login phpmyadmin when I want to see databases,but if I keep seeing the
page over 10 seconds without operation,it will prompt the "token is
overdue",Do anyone know how to configure the time more longer?
Hi,
As I'm doing my final task, which is to remove code duplications and OOping
the code, I came across with a possible idea to re-factor schema exporting
as plugins. That is, as done in "data exporting" with various formats(SQL,
CSV, XML, PDF) the existing schema exporting funcationality would be
implemented as plugins, while preserving OOP concepts.
So this would help in future in such a way, as the modularity and
portability is enhanced, new schema exporting method can be integrated
easily.