No subject


Tue Jul 10 10:02:55 BST 2007


when not set explicitly in the application.

First, is my observation correct?

Second, if not correct, this is less than ideal behavior for an
application I'm writing (on top of a legacy schema) where the primary
key (a compound key = [uid:Integer, gid:Integer]) is in part managed
by the schema itself via postgres triggers.    uid is set by the
trigger, while gid is set explicitly in the application based on
configuration.  Is there an easy way to bypass autofilling?

-- 
d.p.s



More information about the storm mailing list