Re: [SQLObject] bug around datetime default value?

2006-09-15 Thread Ivan Horvath
i've changed mysql table to use NULL as default afterwhile the insert works thank you *** REPLY SEPARATOR *** On 15/09/2006 at 16:35 Oleg Broytmann wrote: >On Fri, Sep 15, 2006 at 02:07:32PM +0200, Ivan Horvath wrote: >> Invalid: expected a datetime in the DateTimeCol 'docDone'

Re: [SQLObject] bug around datetime default value?

2006-09-15 Thread Oleg Broytmann
On Fri, Sep 15, 2006 at 02:07:32PM +0200, Ivan Horvath wrote: > Invalid: expected a datetime in the DateTimeCol 'docDone', got > '-00-00 00:00:00' instead Did MySQL return that instead of NULL? Oleg. -- Oleg Broytmannhttp://phd.pp.ru/[EMAIL PROTECTED]

Re: [SQLObject] bug around datetime default value?

2006-09-15 Thread Ivan Horvath
Best regards, Ivan Horvath Chief Programmer   Alcatel ISD  PMS 2000 Product Team   H-1116, Budapest  Kondorfa u. 10.  Tel.: +36 1 209 9546  Fax.: +36 1 209 9599  Mobil: +36 30 257 0235  VOIP: +49 511 676 478010  [EMAIL PROTECTED] Anyone who has never made a mistake has never tried

Re: [SQLObject] memory leak

2006-09-15 Thread Hiroki Tamakoshi
Thanks Oleg, Dan and Markus!!!, and I could finaly understand the issue. The code by Dan helps me. On Fri, 15 Sep 2006 13:35:25 +0300 Dan Pascu <[EMAIL PROTECTED]> wrote: > If you want to see if you have memory leaks try to run your code in an > infinite loop: > > while 1: > obj_list = []

Re: [SQLObject] memory leak

2006-09-15 Thread Dan Pascu
On Friday 15 September 2006 12:41, Hiroki Tamakoshi wrote: > On Fri, 15 Sep 2006 11:30:11 +0200 > calling gc.collect() doesn't change the memory usage. > (Dan's patch is applied) > > obj_list = [] > for i in xrange( 1000 ): > obj = SomeObject( parameters ... ) > obj_list.append( obj ) #

Re: [SQLObject] memory leak

2006-09-15 Thread Dan Pascu
On Friday 15 September 2006 12:41, Hiroki Tamakoshi wrote: > On Fri, 15 Sep 2006 11:30:11 +0200 > > "Markus Gritsch" <[EMAIL PROTECTED]> wrote: > > Because you cannot explicitely delete an object. By calling del on a > > variable which holds a reference to it, you just remove this > > particular r

Re: [SQLObject] memory leak

2006-09-15 Thread Markus Gritsch
On 9/15/06, Markus Gritsch <[EMAIL PROTECTED]> wrote: > On 9/15/06, Hiroki Tamakoshi <[EMAIL PROTECTED]> wrote: > > > > On Fri, 15 Sep 2006 11:30:11 +0200 > > "Markus Gritsch" <[EMAIL PROTECTED]> wrote: > > > > > Because you cannot explicitely delete an object. By calling del on a > > > variable w

Re: [SQLObject] memory leak

2006-09-15 Thread Markus Gritsch
On 9/15/06, Hiroki Tamakoshi <[EMAIL PROTECTED]> wrote: > > On Fri, 15 Sep 2006 11:30:11 +0200 > "Markus Gritsch" <[EMAIL PROTECTED]> wrote: > > > Because you cannot explicitely delete an object. By calling del on a > > variable which holds a reference to it, you just remove this > > particular re

Re: [SQLObject] memory leak

2006-09-15 Thread Hiroki Tamakoshi
On Fri, 15 Sep 2006 11:30:11 +0200 "Markus Gritsch" <[EMAIL PROTECTED]> wrote: > Because you cannot explicitely delete an object. By calling del on a > variable which holds a reference to it, you just remove this > particular reference to the object. If it was the last reference > pointing to t

Re: [SQLObject] memory leak

2006-09-15 Thread Markus Gritsch
On 9/15/06, Hiroki Tamakoshi <[EMAIL PROTECTED]> wrote: > On Fri, 15 Sep 2006 10:57:31 +0200 > "Markus Gritsch" <[EMAIL PROTECTED]> wrote: > > > del obj_list[:] in your example code is definitely not what you want. > > By [:] you create a copy of your list, and the statement you wrote > > deletes j

Re: [SQLObject] memory leak

2006-09-15 Thread Hiroki Tamakoshi
On Fri, 15 Sep 2006 10:57:31 +0200 "Markus Gritsch" <[EMAIL PROTECTED]> wrote: > del obj_list[:] in your example code is definitely not what you want. > By [:] you create a copy of your list, and the statement you wrote > deletes just this copy. > > In the following example obj_list is still ther

Re: [SQLObject] memory leak

2006-09-15 Thread Markus Gritsch
On 9/15/06, Hiroki Tamakoshi <[EMAIL PROTECTED]> wrote: > Thanks Dan, > > Can I consult with you even if the problem I have is not the problem of > circular references? > > The expected work is clear, and natural I think: > 1. A sqlobject is persistent in RDBMS, > 2. and when I want to delete the o

Re: [SQLObject] memory leak

2006-09-15 Thread Hiroki Tamakoshi
Thanks Dan, Can I consult with you even if the problem I have is not the problem of circular references? The expected work is clear, and natural I think: 1. A sqlobject is persistent in RDBMS, 2. and when I want to delete the object, it is freed from memory(and cache), but its data is still persi