Dan Ch,
Well as you might have noticed the code will work as usual if the
rowid-column field is not specified in jaws.xml. If it is specified, it will
then be used instead of the primary key. I am not sure of how other
databases work with rowids which is why jaws will still default to normal
behaviour.
Do you think we are in a position to submit the source? I'd have rather
sent the modified source files for peer review in case I have goofed up!
And *then* committed changes. Do you have the time to spare?
Regards,
Vinay
----- Original Message -----
From: "danch (Dan Christopherson)" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 06, 2001 9:08 PM
Subject: Re: [JBoss-dev] Fast Updates Based on Row ID
> Just for the record, I don't mind having Oracle specific optimizations
> in JAWS, it's just that the current structure of JAWS does not really
> lend itself to this. Also, if you do use Oracle specific stuff for this
> optimization, the option in a jaws entity should be given a name that
> will tell users clearly that it won't work on other databases.
>
> K.V. Vinay Menon wrote:
>
> > Well,
> > We are an Oracle shop and woudl benefit [like loads of other Oracle
> > users] from these changes. Remember they are there as an option. If you
> > choose not to use them JAWS will work as usual.
> >
> > Vinay
> > ----- Original Message -----
> > From: "Jay Walters" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Wednesday, June 06, 2001 6:18 PM
> > Subject: RE: [JBoss-dev] Fast Updates Based on Row ID
> >
> >
> >
> >>This is oracle specific as far as I know (insert...returning...). The
> >>create problem needs to be addressed if one cannot retrieve the rowid,
the
> >>logic needs to check and see if rowid is set or not - maybe Vinay
already
> >>did this, I didn't look that hard.
> >>
>
>
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
