Boris Duek wrote:
> 2. I was assigning Python-bool value (True,False) to a TINYINT(1)
> column.
>
> But No 2. - maybe sqlalchemy could know that True is "1" and False is
> "0" because MySQL (the database to which I connect) treats its own
> BOOL type as an alias to "TINYINT(1)"?
The Boolean col
Hi Alexandre,
On Aug 4, 2:33 am, Alexandre CONRAD <[EMAIL PROTECTED]> wrote:
> Hello Boris,
>
> I might not be well waken up, but as I'm looking at your generated SA
> logs, it doesn't show that SA updates the row when the data has not
> changed. It only seems to update fields that have changed.
On Aug 4, 2007, at 4:10 AM, Boris Duek wrote:
>
> So - how is it with sqlalchemy and intelligence when writing to an
> instance of orm-mapped class? Does sqlalchemy behave intelligent just
> by coincidence in some cases (like this one) and in other not?
>
it issues an UPDATE to a specific colu
Alexandre CONRAD wrote:
> I might not be well waken up, but as I'm looking at your generated SA
> logs, it doesn't show that SA updates the row when the data has not
> changed. It only seems to update fields that have changed.
Or maybe should I say that I don't see the data beeing updated even
Hello Boris,
I might not be well waken up, but as I'm looking at your generated SA
logs, it doesn't show that SA updates the row when the data has not
changed. It only seems to update fields that have changed.
Or maybe your talking about the empty BEGIN / COMMIT block that is
beeing sent even
