Menu ▾ ▴

#2941 (ok 3.2.4) Statement may not be safe to log in stmt format

3.2.3
fixed
Marc Delisle
None
1
2013-06-11
2009-11-06
Martin
No

Hi,

I have a little problem with phpMyadmin. Everytime when I change some data set via PHPmyadmin it adds A "LIMIT 1" instead of just only use the primary key to identify this unique row. That is the reason you have one, isn't it?

For normal users this behaviour shouldn't be a problem, but if you run a statement based replication it is, and can lead into inconsistency. I get every time this notice: "Statement may not be safe to log in statement format".

Is there a possibility to switch this off?

Regards,
Martin

Discussion

  • Marc Delisle

    Marc Delisle - 2009-11-06

    Moving to bugs. In fact, this LIMIT could be turned off when there is a primary key, but if there isn't, I remember we need the limit to avoid updating or deleting more than one row.

     

  • Marc Delisle

    Marc Delisle - 2009-11-17
    • assigned_to: nobody --> lem9
     

  • Marc Delisle

    Marc Delisle - 2009-11-21
    • milestone: --> 3.2.3
    • priority: 5 --> 1
    • summary: "Statement may not be safe to log in statement format." --> (ok 3.2.4) Statement may not be safe to log in stmt format
    • status: open --> open-fixed
     

  • Marc Delisle

    Marc Delisle - 2009-11-21

    Fixed in subversion, thanks for reporting.

     

  • Marc Delisle

    Marc Delisle - 2009-12-02
    • status: open-fixed --> closed-fixed
     

  • Michal Čihař

    Michal Čihař - 2013-06-11
    • Status: closed-fixed --> fixed