in reply to query problem

The `message_has_been_sent` has been update, while `ml_message` isn't updated.
Considering that one is a table, the other a column name, it's not clear what you mean.

Nor does it seem to be a Perl problem. So, standard questions:

Now, don't go and actually answer the questions here. Answer them for yourself, and if it still puzzled, ask your friendly local dba, or use a MySQL forum.

Replies are listed 'Best First'.
Re^2: query problem
by saintex (Scribe) on Dec 07, 2010 at 12:05 UTC
    please, check the previous answer to corion.
    I have done a type error, while posting my question, but now I correct it:
    The `message_has_been_sent` has been update, while `ml_message` isn't updated.
    It would be:
    The `message_has_been_sent` has been update, while `message_send` isn't updated.

    But, please, "see the moon, not the finger pointing at it".
    before posting this query I checked accuratly some solution.
[reply]

      Please post code that allows us to accurately reproduce your problem. This means, post code that inserts a fresh row and then tries to update the values, and then checks that they have changed. Otherwise, if you do not want us to ask you questions that you are really, really sure do not apply, make sure you have tested them already, and tell us that you have tested them already, and even better, show how you tested these.

      At least from your Perl code, it is still unclear to me why the code you showed would not work, so I assume that the error likely is elsewhere, either in your testing method, in the database or in the code you didn't show.

[reply]

        First of all, I would like to apologize to all for my previous sharp answers, but... I come from three days of debugging in a very large code, in order to discover the error.
        And your first answers sound to me like "you are beginner, please learn SQL and DB management before asking"... not a great answer to have, after serveral days of hard debugging...

        So excuse me for my previous roughness.

        Then, I answer to Marto:

        We aren't sure of anything.
        Me too.. :-) so we are all Socratians... :-)
        I'm asking to you, because I think you are more experienced than me... I thought that problem maybe occurred to something else and so I asked :-).

        By the way, I think that is a very serious bug, and it affects many Red Hat versions (see below)...
        So I thought it may be occurred to someone else.

        if I will know the solution, I'm not be here to ask, but maybe to answer to someone else...
        :-)
        Did you check the change log and bugs relating to this old version of the module?
        yes.
        Maybe it is something like this:
        Fixed DBD::Proxy handling of some methods, including commit and rollback.

        Are you using the system Perl which shipped with RedHat?

        I'm using the system which is shipped with CentOS 5 (Red Hat re-compiled for the community): it follows the Red Hat updates.

        To Corion

        Also, you could install a newer version of DBI yourself, as a test to check whether the error goes away.
        Yes I will try via CPAN, before asking to sysadmin to update the package.
[reply]
        thank you for your answer,

        In my original post now I inserted an update, as you asked me.
        I tried the same code on another machine, with DBI 1.615, and all works fine.
        I think it is something related to DBI 1.52.
        Unlikley DBI 1.52 is the default package on Red Hat Enterprise and CentOS.

        Any suggestions?
[reply]
        thank you for your answer,
        now it is a system problem,
        because DBI 1.52 comes with main Red Hat Enterprise version.

        If I will update the package outside the core distribution, will not be so simple to update the system (via yum).

        Anyway
        Are we sure that the rror is in old-DBI-version?
        Thank you
[reply]

In Section Seekers of Perl Wisdom