Hi Smita,
about this message: "Add unique columns to central list", could you
clarify the meaning?
Is this about adding all columns on which there is a unique index, to
the central list?
--
Marc Delisle (phpMyAdmin)
Hi,
I found out that some bug reports by Scrutinizer are wrong. For example,
in [0], the PHP Analyzer reports that you cannot assign a return value
because mysqli_init() always returns null, which is not the case.
[0]
https://scrutinizer-ci.com/g/phpmyadmin/phpmyadmin/issues/master/files/libr…
--
Marc Delisle (phpMyAdmin)
Hi
I think we need to make a separate page as well to manage the central
columns list. Where user will be able to view the complete list of columns
and add/remove/edit some if needed. I have few question regarding the same:
1. Do We really need a separate page ? or add/remove options on
db_structure and tbl_structure page is sufficient? but no edit option we'll
have in this case.
2. How the page should look ? Similar to tbl_structure page with option to
edit and remove a column from the list ? but this can be very long as one
database in total may have lots many columns. introduce pagination ?
Please share if any other idea ?
Thanks and Regards
- Smita
Hi Smita,
I have a doubt, looking at the structure you chose for this table:
db_name
column_list
This structure implies that, for any change, you have to load a
potentially big row, decode it and encode it. Imagine that there are
hundreds or thousands of column definitions for this db.
I suggest something like:
db_name
column_name
column_attributes
--
Marc Delisle | phpMyAdmin
Hi I need some help here, to implement a drag and drop I need to do some UI
tweak, like there need to be a <div> to be shown in case of dragover event,
and we need another to show the upload status!
Also I need help with design here: How I'm planning it is:
1. User drops a file at any page! (logged in)
2. the dropped files if (sql) are uploaded asynchronously and the status of
upload is shown somewhere in bottom right corner.
3. At the backend the uploaded sql is parsed and output is sent back as
JSON and once the object has been received, the pagecontent is replaced
with the received output! (as happens for any other request in PMA)
I need help with which file I might need to edit, to add a div to the
common UI! for js part I'll add codes to AJAX.js
Also I sent few attachments to the same thread, but I guess moderator needs
to allow it first. It had screenshots of UI I was planning!
Minhaz,
minhaz.cistoner.org || cistoner.org
Hi,
I was looking into RFE: #706. I have attached an image showing a rough idea about its implementation in which we can select multiple databases from the select list. Please comment.
Also I wanted to know if we need this text field next to database select box, after this feature?
Regards,
Ashutosh Dhundhara
Hi developers and especially GSoC students,
if you add an icon, have a look at [0] to learn how to regenerate the
sprites.
[0] https://wiki.phpmyadmin.net/pma/Icons/Sprites_Usage
--
Marc Delisle (phpMyAdmin)
Hi Smita,
I was under the impression that the central list of columns would be
authoritative, regarding the column attributes. Currently, it seems that
the table itself has priority.
For example, if a column is described in the central list as being
VARCHAR(40), and the same column name exists in a table, but with
VARCHAR(45), I would expect a sync operation to adjust the column's size
to the "official" 40. On the contrary, the central list is modified
when doing the sync.
Or, am I mistaken with the goal of the sync feature?
--
Marc Delisle (phpMyAdmin)
Hi,
A random idea came to my mind, I don't know if its applicable or not, I
thought I'd send it in mailing list before sending a feature request!
*Its an improvement to the import feature that exists currently: *
If a user drags and drop a *.sql* file to the pma interface (anywhere) the
interface should import it and execute it. There should not be a condition
that user drops it to import page only. In case db is not selected, we can
show a custom error, otherwise, upload the file asynchronously and execute
the query just like it happens when import is done.
I can't think of a false positive here, as if this feature is implemented
no user is going to accidently drop a sql file into the page!
I'd like to know your opinions about this.
Minhaz,
minhaz.cistoner.org || cistoner.org