Re: CA-Ingres II 2.6 SP2: JDBC EDBC Driver: DatabaseMetaData.getTables() method

This is a discussion on Re: CA-Ingres II 2.6 SP2: JDBC EDBC Driver: DatabaseMetaData.getTables() method within the Ingres Database forums in Other Databases category; I've posted this message on dbForums at URL: http://www.dbforums.com/showthread.p...11#post4376111 -- Jason Tepoorten @HOME +61 433 176 821 (mobile telephone) jason@tepoorten.com 8MP Australia djtep wrote in message news:... > > CA-Ingres II 2.6 SP2: JDBC EDBC Driver: DatabaseMetaData.getTables() method > > -------------------------------------------------------------------------- -- > ---- > > Dear everyone. > > We are experience abnormal behaviour with the CA-Ingres II 2.6 SP2: JDBC > EDBC Driver: DatabaseMetaData.getTables() method. > > Our Environment: > 7 Solaris 8 > 7 CA-Ingres II 2.6 SP2 DBMS > 7 Database with tables using LONG VARCHAR and LONG BYTE > > The DatabaseMetaData.getTables() method includes the iietab tables ...

Go Back   Database Forum > Other Databases > Ingres Database

Database Forums

Register FAQ Calendar Search Today's Posts Mark Forums Read
  #1  
Old 08-02-2005, 08:48 AM
Default Re: CA-Ingres II 2.6 SP2: JDBC EDBC Driver: DatabaseMetaData.getTables() method

I've posted this message on dbForums at URL:
http://www.dbforums.com/showthread.p...11#post4376111

--
Jason Tepoorten
@HOME
+61 433 176 821 (mobile telephone)
jason-at-tepoorten.com
8MP
Australia

"djtep" wrote in message news:...
>
> CA-Ingres II 2.6 SP2: JDBC EDBC Driver: DatabaseMetaData.getTables()

method
>
> --------------------------------------------------------------------------

--
> ----
>
> Dear everyone.
>
> We are experience abnormal behaviour with the CA-Ingres II 2.6 SP2: JDBC
> EDBC Driver: DatabaseMetaData.getTables() method.
>
> Our Environment:
> 7 Solaris 8
> 7 CA-Ingres II 2.6 SP2 DBMS
> 7 Database with tables using LONG VARCHAR and LONG BYTE
>
> The DatabaseMetaData.getTables() method includes the "iietab" tables thare
> the DBMS uses to store LONG VARCHAR and LONG BYTE data.
>
> We believe this is incorrect behaviour given that those tables are not
> intended to be manipulated by applications or DBMS users. These tables are
> for DBMS usage only.
>
> Has anyone experienced this behaviour? Has anyone logged any support calls
> with CA? If so, what is the outcome?
>
> Does anyone have any immediate workarounds?
>
> The issue is inconvenient, where we want to use the dbunit

(www.dbunit.org)
> tool to export data from one database and import to another database.
>
> I am interested in any responses.
>
> Kind Regards,
>
>
> --
> Jason Tepoorten
> @HOME
> +61 433 176 821 (mobile telephone)
> jason-at-tepoorten.com
> 8MP
> Australia
>
>



Reply With Quote
  #2  
Old 08-06-2005, 08:48 AM
Default Re: CA-Ingres II 2.6 SP2: JDBC EDBC Driver: DatabaseMetaData.getTables() method

A support call was raised with Computer Associates and they were able
to provide a patched EDBC.JAR.

--
Jason Tepoorten
@HOME
+61 433 176 821 (mobile telephone)
jason-at-tepoorten.com
8MP
Australia

"djtep" wrote in message
news:1122983121.392833-at-kangaroo.ozonline.com.au...
| I've posted this message on dbForums at URL:
| http://www.dbforums.com/showthread.p...11#post4376111
|
| --
| Jason Tepoorten
| @HOME
| +61 433 176 821 (mobile telephone)
| jason-at-tepoorten.com
| 8MP
| Australia
|
| "djtep" wrote in message news:...
| >
| > CA-Ingres II 2.6 SP2: JDBC EDBC Driver:
DatabaseMetaData.getTables()
| method
| >
|
> --------------------------------------------------------------------

------
| --
| > ----
| >
| > Dear everyone.
| >
| > We are experience abnormal behaviour with the CA-Ingres II 2.6
SP2: JDBC
| > EDBC Driver: DatabaseMetaData.getTables() method.
| >
| > Our Environment:
| > 7 Solaris 8
| > 7 CA-Ingres II 2.6 SP2 DBMS
| > 7 Database with tables using LONG VARCHAR and LONG BYTE
| >
| > The DatabaseMetaData.getTables() method includes the "iietab"
tables thare
| > the DBMS uses to store LONG VARCHAR and LONG BYTE data.
| >
| > We believe this is incorrect behaviour given that those tables are
not
| > intended to be manipulated by applications or DBMS users. These
tables are
| > for DBMS usage only.
| >
| > Has anyone experienced this behaviour? Has anyone logged any
support calls
| > with CA? If so, what is the outcome?
| >
| > Does anyone have any immediate workarounds?
| >
| > The issue is inconvenient, where we want to use the dbunit
| (www.dbunit.org)
| > tool to export data from one database and import to another
database.
| >
| > I am interested in any responses.
| >
| > Kind Regards,
| >
| >
| > --
| > Jason Tepoorten
| > @HOME
| > +61 433 176 821 (mobile telephone)
| > jason-at-tepoorten.com
| > 8MP
| > Australia
| >
| >
|
|


Reply With Quote
Reply


Thread Tools
Display Modes



All times are GMT -4. The time now is 10:00 PM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
Integrated by bbpixel2009 :: jvbPlugin R1013.368.1

Search Engine Friendly URLs by vBSEO 3.1.0
vB Ad Management by =RedTyger=
In an effort to better serve ads to our visitors, cookies are used on Mydatabasesupport.com. For more information, check out our Privacy Policy.