Re: [SQLObject] request for elaboration on code

[Ian B. <ia...@co...>]

jws...@ra... wrote:
> I'm having a hard time getting my head around why SQLOject needs to
> do a select at all. I am trying to create an object- i.e. write a
> row. My data gets written to postgres as I expect, then I get this
> other error complaining about oid's not existing.

SQLObject originally used the more traditional technique of doing 
"SELECT nextval(seq_name)" then using the result to insert into the 
table.  There was a change to using OIDs that meant that we did't have 
to depend on specific sequence names.  But since then there were some 
concerns raised that (as you're finding) some tables don't have OIDs, 
and they aren't indexed by default in all PostgreSQL versions, which 
could lead to some bad performance.

Anyway, I was planning on going back to using sequences, or allowing for 
some other configurable behavior, I just haven't done so yet.

   Ian