Yup, you've got it!! But I thought of another issue that I didn't include
in my re-write (although I'm sure you're already on to it). It must be
possible to set a "REF" field to null as well. The way I reasoned at first
was that no REF should be set to null as it was a foreign key. However, it
now strikes me that as a table can reference other tables
without foreign key. Setting a null value to a foreign key should be
thrown as a violation of db rules, not denied already before insertion.
But as I said, I'm sure you've thought of that :-)
Fredrik...
On Tue, 23 May 2000, Rickard Öberg wrote:
> Hi!
>
> Fredrik Borgh wrote:
> > I'll try to make another re-write of the method using the latest version
> > of JAWSPers..... from the CVS and post it today or tomorrow on Bugzilla.
> > Hopefully, this time it will be used.
>
> I'm actually currently working on it :-) It's the dirtyFields thing,
> right? And the nullpointer fix?
>
> /Rickard
>
> --
> Rickard Öberg
>
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
