niXforums Forum Index
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   PreferencesPreferences   Log in to check your private messagesLog in to check your private messages   Log inLog in 
·  nixdoc.net ·  man pages ·  Linux HOWTOs ·  FreeBSD Tips ·  Forums
navigation Forum index » Databases » rdb
Problems obtaining column length data from ADO.Net
Post new topic   Reply to topic Page 1 of 1 [2 Posts] View previous topic :: View next topic
Author Message
Norman Lastovica
*nix forums beginner


Joined: 22 Jul 2005
Posts: 30

PostPosted: Thu Jan 26, 2006 7:29 pm    Post subject: Re: Problems obtaining column length data from ADO.Net Reply with quote

you best bet here would probably to start with
calling Rdb support directly.

Bob Jarvis wrote:
Quote:

We have a .NET web app which has been working well using a 2.0 version
of the Oracle Rdb ODBC driver. Management has decreed that we must use
the latest 3.0 Oracle Rdb ODBC driver (v3.01.00.02) on a new server.
Here's a code example of what we're doing:

Private pCnn As New OdbcConnection
Dim Ds As DataSet = New DataSet
Dim Da As New OdbcDataAdapter("SELECT * FROM " & TableName, pCnn)

Da.FillSchema(Ds, SchemaType.Mapped, TableName)

Under the 2.0 driver we find that after the FillSchema call all
attributes for columns in the DataSet are properly filled in and we go
on our merry way. When using the 3.0 driver, however, we find that
after FillSchema is called the MaxLength property on all columns in the
DataSet are not set (all are zeroed out), and thus when we try to
assign string values to various columns we get an error saying
something like "Cannot assign XXXXXXXXXXXX to column COLUMN_NAME
because the new value exceeds the maximum length". We thought about
setting the MaxLength property ourselves but found that it is not a
settable property.

We've traced ODBC activity and have found a couple of failures when
ADO.Net is calling SQLColAttribute for attributes 1211 and 1212. I've
found no documentation for what these attribute descriptor numbers
might be, and the values for SQL_DESC_* in SQL.H don't seem to be in
that range.

My questions:
1. Has anyone else encountered this problem? (Surely we're not the
first!)
2. Workaround? Fix?
3. Is this an MS problem or an Oracle problem?
4. Is there a newer version of the Oracle Rdb ODBC driver?

Any help or advice appreciated.

--
- - - - -
opinions expressed here are mine and mine alone
and certainly are not intended in any way to
express or represent any opinions or commitment
of oracle corporation.

norman lastovica / oracle rdb engineering
Back to top
Bob Jarvis
*nix forums beginner


Joined: 25 Jan 2006
Posts: 2

PostPosted: Wed Jan 25, 2006 2:29 pm    Post subject: Problems obtaining column length data from ADO.Net Reply with quote

We have a .NET web app which has been working well using a 2.0 version
of the Oracle Rdb ODBC driver. Management has decreed that we must use
the latest 3.0 Oracle Rdb ODBC driver (v3.01.00.02) on a new server.
Here's a code example of what we're doing:

Private pCnn As New OdbcConnection
Dim Ds As DataSet = New DataSet
Dim Da As New OdbcDataAdapter("SELECT * FROM " & TableName, pCnn)

Da.FillSchema(Ds, SchemaType.Mapped, TableName)

Under the 2.0 driver we find that after the FillSchema call all
attributes for columns in the DataSet are properly filled in and we go
on our merry way. When using the 3.0 driver, however, we find that
after FillSchema is called the MaxLength property on all columns in the
DataSet are not set (all are zeroed out), and thus when we try to
assign string values to various columns we get an error saying
something like "Cannot assign XXXXXXXXXXXX to column COLUMN_NAME
because the new value exceeds the maximum length". We thought about
setting the MaxLength property ourselves but found that it is not a
settable property.

We've traced ODBC activity and have found a couple of failures when
ADO.Net is calling SQLColAttribute for attributes 1211 and 1212. I've
found no documentation for what these attribute descriptor numbers
might be, and the values for SQL_DESC_* in SQL.H don't seem to be in
that range.

My questions:
1. Has anyone else encountered this problem? (Surely we're not the
first!)
2. Workaround? Fix?
3. Is this an MS problem or an Oracle problem?
4. Is there a newer version of the Oracle Rdb ODBC driver?

Any help or advice appreciated.
Back to top
Google

Back to top
Display posts from previous:   
Post new topic   Reply to topic Page 1 of 1 [2 Posts] View previous topic :: View next topic
The time now is Sat Nov 22, 2008 11:26 am | All times are GMT
navigation Forum index » Databases » rdb
Jump to:  

Similar Topics
Topic Author Forum Replies Last Post
No new posts Winbind problems for ADS authentication nlinley networking 1 Tue Sep 19, 2006 9:22 am
No new posts Bug#379103: ITP: complearn-gui -- 3D drag-and-drop interf... Rudi Cilibrasi devel 0 Fri Jul 21, 2006 11:00 am
No new posts problems using oddmuse with mod_perl2 inside apache2.2 pe... Fergus McMenemie Perl 0 Fri Jul 21, 2006 9:48 am
No new posts Bug#379087: ITP: libcomplearn -- data-compression based i... Rudi Cilibrasi devel 0 Fri Jul 21, 2006 7:40 am
No new posts Problems with make-kpkg and skas patch Todd A. Jacobs Debian 0 Fri Jul 21, 2006 12:30 am

Myspace Backgrounds | Credit Cards UK | Loans | Car Loan | Share Prices
Copyright © 2004-2005 DeniX Solutions SRL
 
Other DeniX Solutions sites: Unix/Linux blog |  electronics forum |  medicine forum |  science forum | 
Privacy Policy


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.2381s ][ Queries: 20 (0.1337s) ][ GZIP on - Debug on ]