db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernt M. Johnsen" <Bernt.John...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-104) Get rid of the Max lenght of 18 for constraint names
Date Mon, 09 May 2005 07:49:22 GMT

Thanks for you answer,

>>>>>>>>>>>> Daniel John Debrunner wrote (2005-05-06 06:47:41):
> Bernt M. Johnsen (JIRA) wrote:
> >      [ http://issues.apache.org/jira/browse/DERBY-104?page=comments#action_64618
> >      
> > Bernt M. Johnsen commented on DERBY-104:
> > ----------------------------------------
> > 
> > There seems to be no (practical) limit on cursor names:
> >  get cursor zzzz as 'select * from tab';
> > where zzzz is 10000 characters long works prefectly in ij (same goes for next etc).
> Just to be clear that GET CURSOR is a feature of ij only, it is not SQL.
> It's an interface to the JDBC cursor mechanism, so any limit on cursor
> names would come from the JDBC spec.

I'm fully aware that GET CURSOR is not SQL. I just assumed that the
cursor name would propagate down from the JDBC driver to some lower
layer and that assumption was obviously wrong.

> I think it was a mistake for ij to have these special commands that
> allowed testing of JDBC features from ij. Some, like this one, look like
> SQL and thus users have sometimes been suprised that they were not
> supported by the engine itself.
> I think a better approach would have been to write tests that used JDBC
> directly (.java tests), this also mimics how actual applications would
> use those features.

Bernt Marius Johnsen, Database Technology Group, 
Sun Microsystems, Trondheim, Norway

View raw message