I've been thinking to extend 'select-for-update' support so that you could
easily define it in the type-mappings.
Maybe one of my earlier posts has relevence to this?
> What do you think of these ideas? What I wanted to do was extend the
> database typemappings in standardjaws.xml.
>
> <type-mappings>
> <type-mapping-definition>
> <name>Oracle8</name>
>
> <select-for-update-supported>true</select-for-update-supported>
> <select-for-update-format>![CDATA[SELECT %i FROM
> %t WHERE %w FOR
> UPDATE]]</select-for-update-format>
> <select-for-update-no-wait-supported>true</select-for-update-supported>
> <select-for-update-no-wait-format>![CDATA[SELECT
> %i FROM %t WHERE %w
> FOR
> UPDATE NOWAIT ]]</select-for-update-format> <mapping>
> <java-type>java.lang.Boolean</java-type>
> <jdbc-type>BIT</jdbc-type>
> <sql-type>SMALLINT</sql-type>
> </mapping>
>
> where "%i" is the items to be select, "%t" is the tablename, and
> "%w" is the
> where clause. If a bean turns on select-for-update and it is not
> supported
> by the type-mapping, then an exception should be thrown on deployment.
> Maybe your rowid thingy should be put in there as well in the same manner.
>
> And then in jaws.xml
>
> <select-for-update wait="true">true</select-for-update>
Regards,
BIll
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jay
> Walters
> Sent: Friday, August 17, 2001 3:46 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: [JBoss-dev] JDBC SQL Extensions
>
>
> Suppose it depends where you start. As somebody with 14 years of Oracle
> experience the {oj} example you gave makes no sense to me, so it
> is both not
> concise nor not understandable.
>
> But lets not make this a pissing contest. I agree with you. I think the
> core fact is that for a variety of reasons most database vendors really
> don't implement all the standards in such a way that a user can take a
> real-world application and just move it from one database to the next.
>
> For that reason, I think you're going to need some mapping from EJB-QL to
> the various SQL dialects.
>
> Cheers
>
> -----Original Message-----
> From: Dain Sundstrom [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 17, 2001 3:39 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] JDBC SQL Extensions
>
>
> consice does not equal understandable
>
> for example
>
> a?b:c
>
> -dain
> ----- Original Message -----
> From: "Jay Walters" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, August 17, 2001 2:16 PM
> Subject: RE: [JBoss-dev] JDBC SQL Extensions
>
>
> > Not to be too much in oracle's defense, but their proprietary outer join
> > syntax is much more concise. I think you will need to do
> mapping onto the
> > various vendor's syntax...
> >
> > -----Original Message-----
> > From: Dain Sundstrom [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, August 17, 2001 3:11 PM
> > To: [EMAIL PROTECTED]
> > Subject: [JBoss-dev] JDBC SQL Extensions
> >
> >
> > all JDBC experts,
> >
> > Is it common for the JDBC drivers to support the SQL Extension
> functions?
> > http://java.sun.com/j2se/1.3/docs/guide/jdbc/spec/jdbc-spec.frame11.html
> >
> > I specifically need the functions: concat, substring, locate,
> length, abs,
> > and sqrt.
> >
> > I'm planing on mapping these to {fn concat('str1', 'str2')} style
> functions.
> > If it is not common to support these fuctions I'll write a function map
> spec
> > in the xml.
> >
> > Also, do most vendors support the {oj outer-join} syntax like:
> >
> > SELECT *
> > FROM {oj order LEFT OUTER JOIN line_item ON
> > order.ordernumber=line_item.ordernumber}
> >
> > I think I need this to support the IS EMPTY operator in queries like:
> >
> > SELECT OBJECT(o)
> > FROM Order o
> > WHERE o.lineItems IS EMPTY
> >
> >
> > Thanks for any help
> >
> > -dain
> >
> > P.S. I just found some docs that say that Oracle drivers do not support
> any
> > of these "portability features" (my words). Does anyone find this
> > supprising? (I'll keep my feelings on this to my self). Any
> way, if it is
> > true, I'll implement this the hard way after I get the easy way working.
> >
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-development
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-development
> >
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
