<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Fri, May 23, 2014 at 2:45 AM, 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:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Le 2014-05-22 15:25, Smita a écrit :<br>
<div>><br>
> On Thu, May 22, 2014 at 10:44 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>
> Hi Smita,<br>
><br>
> I was under the impression that the central list of columns would be<br>
> authoritative, regarding the column attributes. Currently, it seems that<br>
> the table itself has priority.<br>
><br>
> For example, if a column is described in the central list as being<br>
> VARCHAR(40), and the same column name exists in a table, but with<br>
> VARCHAR(45), I would expect a sync operation to adjust the column's size<br>
> to the "official" 40. On the contrary, the central list is modified<br>
> when doing the sync.<br>
><br>
> Hi Marc,<br>
> In my opinion, changing type without user consent is not a good idea.<br>
> there might be a case that, in one table let say 'id' field needs INT<br>
> but in another table which expected to have lot more rows will need<br>
> field 'id' to be of type BIGINT. So in this case if system changes<br>
> BIGINT to INT, it would be big problem. If I understood you correctly.<br>
<br>
</div>In this case, in the central list, 'id' should be defined as BIGINT, and<br>
the central definition should be the one that is applied to a table,<br>
when someone asks to synchronize this table.<br>
<br>
Now, what kind of user confirmation should be asked in this case, is up<br>
to you.<br>
<br>
Maybe, calling this feature "Sync" is misleading, and we need two<br>
different features. One that would populate the central list, starting<br>
from a particular table (but should notify the user in case a column<br>
name already exists in the central list).<br>
<br></blockquote><div>We can just say, Add unique columns to central list instead of saying "Sync" . <br></div><div>So if user chooses a table to add its columns to the central, and some column of this table already exist in the central then we show columns col1, col3 already exist so is not updated ?<br>
<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
And another feature that applies the central list definitions to a<br>
chosen table (or just verifies and notifies the user if a central<br>
definition is found for one of the columns in this table).<br>
<div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div> </div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
><br>
> Or, am I mistaken with the goal of the sync feature?<br>
><br>
><br>
> I think my understanding of the problem [0] is somewhat different from<br>
> what you have understood. What I understood from the problem that some<br>
> of the already existing columns from the database, we keep in a central<br>
> list. and then while making a new table or adding a new column to a<br>
> existing table, from the central list we can pick a column using option<br>
> on UI which autopopulate all the fields for new column being added. So<br>
> if there is already a existing column let say 'product_id', while adding<br>
> new similar column in some table user won't use prod_id or something<br>
> similar with different attributes, they can just select 'product_id'<br>
> from central list. It also saves user from filling all the necessary fields.<br>
<br>
</div>Yes, but this will be done in a different task in your schedule, correct?<br><div></div></blockquote><div><br></div><div>Yes you are right, I'll start that in coming week. All that i have done so far is just to populate the central list. In that also, eliminating duplicates, showing appropriate messages while adding/removing column, writing documentation for the new configuration directive still need to be done for this week. <br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
> So in my implementation Syncing a table meant: just adding columns with<br>
> unique attributes ( not matching with any other column in central list )<br>
> of that table in the central list.<br>
<br>
</div>Please try the case when a column already exists in the central list. In<br>
my test, this column was updated in the central list but it's not always<br>
the best thing to do,<br></blockquote><div> </div><div>Ok. So if a column is already existing and user tries to add same column again, We will show error saying column already exist. If they still want to update, they need to first remove that column and then add ?.<br>
<br></div><div>Similarly if a columns has never added and being tried to remove, we show error saying column doesn't exist in central list.<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
><br>
> Please let me know if I'm interpreting the problem[0] wrongly.<br>
><br>
> [0] <a href="http://sourceforge.net/p/phpmyadmin/feature-requests/1477/" target="_blank">http://sourceforge.net/p/phpmyadmin/feature-requests/1477/</a><br>
<br>
<br>
--<br>
</div><span><font color="#888888">Marc Delisle | phpMyAdmin<br>
</font></span><div><div><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><br></div></div>