On Feb 18, 2008, at 6:16 PM, Adrian Klaver wrote:
> The problem is that the transaction does not commit. When I move off
> the record I get the
> confirmation dialog asking it I want to save my changes. If I answer
> yes I get:
>
> statement: update "public"."projection" set "sub_method" = 'none',
> "p_item_no" = 1, "line_id" = 12143, "c_id" = '35RF', "qty" =
> 10.0000, "trial" = NULL, "link_key" = NULL, "year" = '2008',
> "proj_note" = NULL, "method" = 'seed', "dabo-tmpKeyField" = NULL,
> "item_key" = NULL, "pot_ct" = NULL where
> "public"."projection"."line_id"=-1
> postgres-production-2008-02-18 16:05:30.828
>
> PSTERROR: column "dabo-tmpKeyField" of relation "projection" does
> not exist at character 218
>
> Note the dabo-tmpKeyField field in the Insert statement.
That's really odd - I've tested with MySQL and SQLite, and don't see
this behavior on either. Can you try this: after saving the new
record, open up a command window and type:
print self.PrimaryBizobj.isAnyChanged()
If that returns True, then try these two:
biz = self.PrimaryBizobj
print "NEW", biz._CurrentCursor._getNewRecordDiff(biz.RowNumber)
print "UPD", biz._CurrentCursor.getRecordStatus(biz.RowNumber)
Let me know what you get.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
