On Sat, May 24, 2014 at 7:49 PM, Marc Delisle marc@infomarc.info wrote:
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
Yeah, agree. Thanks, It would be better to keep this. :-).
I have a question: If we have "id interger(11) not null auto_increment" already existing in central list, should we allow to add another column "id integer(20) not null auto_increment" ? If we don't allow then we can also keep structure like maybe: db_name column_name column_type column_collation column_isNull column_extra
- Smita
--
Marc Delisle | phpMyAdmin
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel