On Sep 26, 2007, at 9:28 AM, Barry Hart wrote:
My application has a table of item prices by week. A record is
inserted into a week whenever there is a new, different price. To
find the current price, you have to look backwards in time to the
most recent record.
I've written some code
On Sep 25, 2007, at 7:30 PM, m h wrote:
Have updated the ticket with my fix change the dbapi_type of
OracleText from CLOB to NUMBER I'm not sure if this breaks others
code
the bug is, the type of the bind parameters should be coming out as
VARCHAR, not CLOB. NUMBER is
On 9/26/07, Michael Bayer [EMAIL PROTECTED] wrote:
On Sep 25, 2007, at 7:30 PM, m h wrote:
Have updated the ticket with my fix change the dbapi_type of
OracleText from CLOB to NUMBER I'm not sure if this breaks others
code
the bug is, the type of the bind parameters
On Sep 25, 2007, at 12:15 PM, [EMAIL PROTECTED] wrote:
anyway, all 10328 (joined) cases pass, have a nice day.
svilen
ive changed my approach on this one to what i should have done in the
1st place. try out 3518.
--~--~-~--~~~---~--~~
You received this
It seems that something changed in 0.4 that causes server-side cursors
(in postgresql) to fail. I'm issuing the DECLARE/FETCH commands
manually through connection.execute, not using server_side_cursors in
the dialect, since I only want certain queries to use them. I verified
that this works on
On Wednesday 26 September 2007 20:09:10 Michael Bayer wrote:
On Sep 25, 2007, at 12:15 PM, [EMAIL PROTECTED] wrote:
anyway, all 10328 (joined) cases pass, have a nice day.
svilen
ive changed my approach on this one to what i should have done in
the 1st place. try out 3518.
ok too now,
cursor.description isn't available after the DECLARE (analogous to
conn.cursor(x)), but is available after a FETCH (analogous to a
cur.fetchXXX()). If you want to get rid of the buffering resultproxy,
you can do a FETCH ABSOLUTE 0 FROM cursor_name - that will make
cursor.description available,
On Sep 26, 2007, at 5:31 PM, Dan Watson wrote:
cursor.description isn't available after the DECLARE (analogous to
conn.cursor(x)), but is available after a FETCH (analogous to a
cur.fetchXXX()). If you want to get rid of the buffering resultproxy,
you can do a FETCH ABSOLUTE 0 FROM
On Sep 26, 2007, at 5:31 PM, Dan Watson wrote:
cursor.description isn't available after the DECLARE (analogous to
conn.cursor(x)), but is available after a FETCH (analogous to a
cur.fetchXXX()). If you want to get rid of the buffering resultproxy,
you can do a FETCH ABSOLUTE 0 FROM
This should hopefully be the last of the beta releases before 0.4.0
is released. The big change in this one is that the ORM Session is
now *weak referencing* by default, with an option to turn on the old
strong referencing behavior. This means that objects in the
session get cleared out
Dear Micheal,
Does this mean that with web apps since the session is now weak
referencing that we will no longer have to call Session.remove() to
clear out Sessions? Specifically I'm referencing what Mike Orr wrote in
the pylonscookbook.
Jose
Michael Bayer wrote:
This should hopefully be the
11 matches
Mail list logo
