<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, May 24, 2014 at 11:53 PM, Smita <span dir="ltr"><<a href="mailto:kumarismita62@gmail.com" target="_blank">kumarismita62@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Sat, May 24, 2014 at 10:25 PM, Marc Delisle <span dir="ltr"><<a href="mailto:marc@infomarc.info" target="_blank">marc@infomarc.info</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Le 2014-05-24 12:16, Smita a écrit :<br>
<div>><br>
><br>
> On Sat, May 24, 2014 at 9:24 PM, Marc Delisle <<a href="mailto:marc@infomarc.info" target="_blank">marc@infomarc.info</a><br>
</div><div>> <mailto:<a href="mailto:marc@infomarc.info" target="_blank">marc@infomarc.info</a>>> wrote:<br>
><br>
> Le 2014-05-24 11:03, Smita a écrit :<br>
> ><br>
> ><br>
> > On Sat, May 24, 2014 at 7:49 PM, Marc Delisle <<a href="mailto:marc@infomarc.info" target="_blank">marc@infomarc.info</a><br>
> <mailto:<a href="mailto:marc@infomarc.info" target="_blank">marc@infomarc.info</a>><br>
</div><div><div>> > <mailto:<a href="mailto:marc@infomarc.info" target="_blank">marc@infomarc.info</a> <mailto:<a href="mailto:marc@infomarc.info" target="_blank">marc@infomarc.info</a>>>> wrote:<br>
> ><br>
> > Hi Smita,<br>
> > I have a doubt, looking at the structure you chose for this table:<br>
> > db_name<br>
> > column_list<br>
> ><br>
> > This structure implies that, for any change, you have to load a<br>
> > potentially big row, decode it and encode it. Imagine that<br>
> there are<br>
> > hundreds or thousands of column definitions for this db.<br>
> ><br>
> > I suggest something like:<br>
> ><br>
> > db_name<br>
> > column_name<br>
> > column_attributes<br>
> ><br>
> > Yeah, agree. Thanks, It would be better to keep this. :-).<br>
> > I have a question: If we have "id interger(11) not null<br>
> auto_increment"<br>
> > already existing in central list, should we allow to add another<br>
> column<br>
> > "id integer(20) not null auto_increment" ? If we don't allow then<br>
> we can<br>
> > also keep structure like maybe:<br>
> > db_name<br>
> > column_name<br>
> > column_type<br>
> > column_collation<br>
> > column_isNull<br>
> > column_extra<br>
> ><br>
> > - Smita<br>
> ><br>
><br>
> In a central list, there should be only one column named "id" (but this<br>
> choice of name would be problematic, of course; a better choice would be<br>
> "customer_id").<br>
><br>
> So We'll allow only unique column name. If same column name with<br>
> different definition tried to add we just show the column name (with<br>
> defination) already exist?<br>
<br>
</div></div>Yes; eventually I guess that in your project, there will be a way to<br>
directly view the central list and change column definitions.<br>
<div><div><br></div></div></blockquote></div></div><div>Yeah, I need to make a page to manage central columns, there users can view complete list of columns and edit some if they want.<br><br></div><div class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div>
><br>
> Another example is "phone_number"; which is reused in the customer table<br>
> and in the salesperson table. You might want to always use CHAR(25) for<br>
> phone numbers.<br>
><br>
> So it's a good idea to split the attributes into separate columns like<br>
> in your example. The default value could be there too.<br>
><br>
> Ok, thanks. We'll keep default as well.<br>
<br>
<br></div></div></blockquote></div></div></div></div></blockquote><div>Hi Marc,<br></div><div>I redesigned the database as discussed. I completed the adding columns part but I got stuck when came to deletion. I have a question.<br>
</div><div>Let say I have two tables tbl1 and tbl2, both table has a common column name "phone_number". So If user selects both tables and asks to add unique columns to central list, then we are gonna add just one "phone_number" , let say we add the column/definition "phone_number" from tbl1. now let say user select tbl2 and ask to remove columns from central list. What should it do ? should it remove the column "phone_number" from central list or not ? as "phone_number" was added from tbl1. but "phone_number" exists in tbl2 as well.<br>
<br></div><div>- Smita<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
--<br>
Marc Delisle | phpMyAdmin<br>
<br>
------------------------------------------------------------------------------<br>
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE<br>
Instantly run your Selenium tests across 300+ browser/OS combos.<br>
Get unparalleled scalability from the best Selenium testing platform available<br>
Simple to use. Nothing to install. Get started now for free."<br>
<a href="http://p.sf.net/sfu/SauceLabs" target="_blank">http://p.sf.net/sfu/SauceLabs</a><br>
_______________________________________________<br>
Phpmyadmin-devel mailing list<br>
<a href="mailto:Phpmyadmin-devel@lists.sourceforge.net" target="_blank">Phpmyadmin-devel@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel</a><br>
</div></div></blockquote></div></div><br></div></div>
</blockquote></div><br></div></div>