java.util.NoSuchElementException thrown by driver
From: Mark Lewis (mark.lewis_at_mir3.com)
Date: 08/26/04
- Next message: Martin Kultermann: "Transliteration Failed Error in PreparedStatement.setCharacterStre"
- Previous message: Joe Weinstein: "Re: Passing DB Name/Owner Name in a prepareCall statement"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 25 Aug 2004 17:33:51 -0700
Calling connection.prepareStatement(" "); throws a
NoSuchElementException instead of something legitimate,
like a SQLException.
This is just a simple bug, but since I can't figure out how
to report it to Microsoft any other way and couldn't find
anything in the MSDN about it, I decided to post about it here.
The full stack trace is:
java.util.NoSuchElementException
at
java.util.StringTokenizer.nextToken(StringTokenizer.java:259)
at
com.microsoft.jdbc.base.BaseSQLStringGenerator.generateSQL(Unknown
Source)
at com.microsoft.jdbc.base.BaseSQL.getVerb(Unknown
Source)
at
com.microsoft.jdbc.base.BaseSQL.resultType(Unknown Source)
at
com.microsoft.jdbc.base.BaseSQL.processSQL(Unknown Source)
at com.microsoft.jdbc.base.BaseSQL.<init>(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.preProcessSQL(Unknown
Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.<init>(Unknown
Source)
at
com.microsoft.jdbc.base.BaseConnection.prepareStatement(Unknown
Source)
at
com.microsoft.jdbc.base.BaseConnection.prepareStatement(Unknown
Source)
at MyCode
-- Mark Lewis
- Next message: Martin Kultermann: "Transliteration Failed Error in PreparedStatement.setCharacterStre"
- Previous message: Joe Weinstein: "Re: Passing DB Name/Owner Name in a prepareCall statement"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|