[Phpmyadmin-devel] Re: Tr: Bug in phpMyAdmin 2.3.1-dev

[Kyriakos Xagoraris]

Hi Marc,

in the example table I did in phpmyadmin.net (which is now gone - I can create it again if you wish), I used only one table. In my local databases tho the relations were between 2, 3 or in some cases more tables. In all cases the same thing happened. All fields after the first one which had a dropdown list, were converted to dropdown lists which had no values.
Let me know if you'd like me to create the tables at phpmyadmin.net so that you can check it out.

Best Regards,
Kyriakos


> Hi,
>  
>  Kyriokos, as I understand your message, you are setting a relation from 
>  a field to another field in the same table?
>  
>  Marc
>  
>  Loic wrote:
>  
>  > Hi List!
>  > 
>  > Here is a message I received from the phpMyAdmin
>  > Greek translator about a problem he faced.
>  > 
>  > ----------
>  > De: Kyriakos Xagoraris <theremon at th...>
>  > A: lolo at ph...
>  > Date: 10/09/02
>  > Objet: Bug in phpMyAdmin 2.3.1-dev
>  > 
>  > Hi there,
>  > 
>  > I didn't know exactly whom I am supposed to contact about 
>  > this, so please forgive the intrusion if you're not the right 
>  > person.
>  > 
>  > My name is Kyriakos, I'm the guy who's been doing the 
>  > Greek language translations for the past few version and an 
>  > avid PMA user. I download the new releases all the time and 
>  > test them out. A few hours ago I downloaded the latest dev 
>  > release of 2.3.1 release on Sep 5th. Having set up a special 
>  > PMA db in order to use the relation views, pdf etc, I started 
>  > browsing my databases to check the new stuff you guys are 
>  > coding.
>  > 
>  > While browsing a database, I saw a record I wanted to edit in 
>  > a table that I had set relations for. I clicked the 'Edit' link and 
>  > once the edit page loaded, everything was wrong. From what 
>  > it seems, the dropdown feature messes everything up. The 
>  > fields I had created the relations for where the 2nd and 3rd 
>  > fields in the table. 
>  > 
>  > The problem was this: First of all the dropdown lists appeared 
>  > as they should, but they didn't have the appropriate value pre-
>  > selected (I don't know if it should be). Secondly, all fields after 
>  > these two were blank dropdown lists. These fields should be 
>  > text fields or numeric or varchar etc. But they were just empty 
>  > dropdown lists.
>  > 
>  > Since according to the changelog you have done further work 
>  > since Sep. 5th, I tried this on the demo server you have on 
>  > phpmyadmin.net. I created a new table (I named it tdktest) 
>  > and added an smallint field, a text field, a second smallint 
>  > field, and the two more text fields. I then related the second 
>  > smallint field with the first one. Once I tried to edit a record in 
>  > the table, all fields after the second smallint field where empty 
>  > dropdown lists. The text field before it was ok.
>  > I did not drop the table in order for you to check it out. I know 
>  > that all this is still under construction, but I thought I'd let you 
>  > guys know.
>  > 
>  > That's all I guess. Keep up the good work :)
>  > 
>  > Best regards, 
>  > Kyriakos
>  
 > 
>  -- 
>  Marc Delisle

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.phpmyadmin.net/pipermail/developers/attachments/20020911/0f2cdf9f/attachment.html>