On Saturday 03 February 2007 16:02, johnf wrote:
> On Saturday 03 February 2007 15:29, Paul McNett wrote:
> > Paul McNett wrote:
> > > johnf wrote:
> > >>> Normally, after a requery we'd expect to see [] as the return from
> > >>> getChangedRows(), and {} as the return from cur._mementos.
> > >>> bo = self.getBizobj()
> > >>> print bo.getChangedRows()
> > >>
> > >> [0]
> > >>
> > >>> cur = bo._CurrentCursor
> > >>> print cur._mementos
> > >>
> > >> {38714: {'status': None, 'pack2': None, 'mailnotes': None, 'pack1':
> > >> None, 'invlang': None, 'doc2': None, 'doc1': None, 'maddress1': None,
> > >> 'mzip': None, 'mcity': None, 'ship1': None, 'maddress2': None,
> > >> 'notes1': None, 'continent': None, 'mstate': None, 'ship2': None}}
> > >
> > > Ok, thanks John. This confirms what you said: fields were NULL in the
> > > backend, they came over as None in Python, Dabo at some level couldn't
> > > handle it, an error was raised, and the current field values are
> > > probably something other than None (best guess is the empty string).
> > > The memento would have been filled out in setFieldVal(), and that was
> > > probably a result of something behind the scenes in Dabo.
> > >
> > > I'll try to make some time today to write a testcase for this which
> > > will lead to the fix. Thanks!
> >
> > John, please update from svn and try again. I believe there's a high
> > probability I've fixed your problem.
>
> Simple testing reveal no problems. Thanks for fixing this.
Damm I spoke to soon. I'm still having the same problem. Used your test with
the Bizobj and cur and got the same results. Rememeber I'm using Postgres.
Could it be that dbPostgres.py is returning something incorrectly?
--
John Fabiani
_______________________________________________
Post Messages to: Dabo-dev@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
