I'm still having this problem Andy described. Is there a proper solution for this issue meanwhile?
Am Donnerstag, 28. Februar 2008 22:53:07 UTC+1 schrieb Derek Williams: > > On 2008-02-28 12:13, Andy wrote: > > > >I've created a view (with rules to make it writeable) in my Postgres > >database, but I can't currently use it with Sequel because of the way > >in which Sequel tries to automagically determine what the sequence on > >the pkey is called. Would it be possible to add functionality that > >would allow me to custom define pkey/sequences on models - or is there > >a workaround for it that I've missed? > > > >- Andy. > > I had this same problem before as well, andperhaps the proper way for > sequel to do this is to use the 'RETURNING' syntax for inserts. There is > already a bug filed for it, but no one as of yet has written a patch. > That would not completely solve this problem though, there would also > have to be a way of customizing the RETURNING statement. > > The way I dealt with this problem is just handled the error with > begin...rescue...end. The error happens after the row is inserted, so > depending on what you are doing this shouldn't be a problem. > > -- > Derek Williams > > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
