On 20.12.2007 22:46 CE(S)T, Martijn Tonies wrote:
>> Okay, I got that. So a COMMIT statement after disabling autocommit mode
>> and another START TRANSACTION does not finish my transaction. (But then,
>> what does?) Interesting view, I didn't know that. But now all's clear: I
>> won't touch autocom
> >> So MySQL does support nested transaction and both "SET AUTOCOMMIT = 0"
> >> and "START TRANSACTION" start a new transaction level, is that true?
> >
> > I didn't say it supports nested transactions, I said that if your
> > application
> > starts a single transaction and does not finish it, it
On 20.12.2007 21:34 CE(S)T, Martijn Tonies wrote:
>> So MySQL does support nested transaction and both "SET AUTOCOMMIT = 0"
>> and "START TRANSACTION" start a new transaction level, is that true?
>
> I didn't say it supports nested transactions, I said that if your
> application
> starts a single
On 20.12.2007 22:18 CE(S)T, Baron Schwartz wrote:
> On Dec 20, 2007 3:33 PM, Yves Goergen <[EMAIL PROTECTED]> wrote:
>> I wasn't able to find MVCC-related information (I assume it means Multi
>> Version Concurrency Control, not sure whether that's correct) in the
>> MySQL manual. But Martijn's expl
Hi,
On Dec 20, 2007 3:33 PM, Yves Goergen <[EMAIL PROTECTED]> wrote:
> On 20.12.2007 21:14 CE(S)T, Baron Schwartz wrote:
> > It doesn't support nested transactions. What you're seeing is the
> > effects of MVCC. The InnoDB section of the MySQL manual explains it.
>
> I wasn't able to find MVCC-r
> On 20.12.2007 20:34 CE(S)T, Martijn Tonies wrote:
> > Are your tables InnoDB? If so, the snapshot transaction is giving you
> > a static view on the data and your own changes, while your PHPMyAdmin
> > commits the NULL write. Your application keeps on seeing your own
> > changes, cause it did
On 20.12.2007 21:14 CE(S)T, Baron Schwartz wrote:
> It doesn't support nested transactions. What you're seeing is the
> effects of MVCC. The InnoDB section of the MySQL manual explains it.
I wasn't able to find MVCC-related information (I assume it means Multi
Version Concurrency Control, not su
On 20.12.2007 20:34 CE(S)T, Martijn Tonies wrote:
> Are your tables InnoDB? If so, the snapshot transaction is giving you
> a static view on the data and your own changes, while your PHPMyAdmin
> commits the NULL write. Your application keeps on seeing your own
> changes, cause it did not end the s
Hi,
On Dec 20, 2007 2:26 PM, Yves Goergen <[EMAIL PROTECTED]> wrote:
> On 20.12.2007 19:42 CE(S)T, Yves Goergen wrote:
> > But when I set that column to NULL
> > with phpMyAdmin, my application still reads the old data from the
> > database. phpMyAdmin keeps telling me that the value is actually N
Yves,
> On 20.12.2007 19:42 CE(S)T, Yves Goergen wrote:
> > But when I set that column to NULL
> > with phpMyAdmin, my application still reads the old data from the
> > database. phpMyAdmin keeps telling me that the value is actually NULL,
> > which I just entered. Whereas the persistent PHP conn
On 20.12.2007 19:42 CE(S)T, Yves Goergen wrote:
> But when I set that column to NULL
> with phpMyAdmin, my application still reads the old data from the
> database. phpMyAdmin keeps telling me that the value is actually NULL,
> which I just entered. Whereas the persistent PHP connection doesn't see
Hi,
today I have noticed a strange bug with MySQL and PHP. I'm developing a
PHP application, using the MySQL database server 5.0.45 on Windows XP
and the PDO connection objects (PHP Data Objects). The PHP application
works on InnoDB tables and uses transactions and persistent connections.
One of t
12 matches
Mail list logo
