firebird-odbc-devel — All about development of Firebird ODBC driver donated by IBPhoenix

[Firebird-odbc-devel] ODBC driver changes

[Paul R. <pr...@ib...>]

Well, I've finally managed to collate all the contributions that have 
been made to the driver recently.

The changes have been committed to the source tree. Now, we need to test 
them. The only guarantee at the moment is that the code compiles.

I have deliberately chosen to get the changes committed before testing 
them properly because there are several people working on the code at 
the moment and we are in danger of tripping over ourselves. This will 
give everyone a chance to re-sync.

All the changes have been clearly documented. Where code has been 
removed I have commented it out and marked it thus:

   //Orig.

After the removed code I have inserted the suggested changes, starting 
with a brief comment to attribute the change to its owner. Each changed 
file has an amended header summarizing the changes and there is now a 
change log, which you can see below.

Hopefully it will be clear enough to understand what has changed and 
why. For now, we need developers with access to MSVC to actually test 
the changes. There is not much point in testing without the ability to 
trace through the debug code at this stage.

I know there are some more changes in the pipeline. When they are in I 
will look to getting a snapshot beta release out for more widespread 
testing.

Thanks to everyone who has contributed.

Here is the change log:

  * 2002-05-21	BinaryBlob.cpp
  *		Change release() to test useCount <=0
  *	

  * 2002-05-20	Updated OdbcStatement.cpp
  *
  *		Contributed by Robert Milharcic
  *		o Several changes to allow reading of binary blobs
  *		  See code commented with //Added by RM or //From RM

  * 2002-05-20	BinaryBlob.cpp
  *
  *		Contributed by Robert Milharcic
  *		o Start with useCount of 0

  * 2002-05-20	IscConnection.cpp
  *		
  *		Contributed by Robert Milharcic
  *		o better management of statements

  * 2002-05-20	OdbcEnv.cpp
  *
  * 		Contributed by Robert Milharcic
  *		o allocHandle() - Fix typo in assignment to connections

  * 2002-05-20	IscProcedureColumnsResultSet.cpp
  *
  * 		Contributed by C. G. Alvarez
  *		o qualify the column names in getProcedureColumns()

  * 2002-05-20	IscIndexInfoResultSet.cpp
  *
  *		Contributed by ?
  *		o qualify the column names in getIndexInfo()

  * 2002-05-20	Value.cpp
  *		Contributed by Bernhard Schulte
  *		o Updated setValue() to support changes
  *		  in timestamp conversion.	

  * 2002-05-20	TimeStamp.cpp
  *		Contributed by Bernhard Schulte
  *		o Bring operator() up-to-date with timestamp changes.
  *		o ditto decodeTime().

  * 2002-05-20	IscStatement.cpp
  *
  *		Added contributions from Bernhard Schulte
  *		o ::setValue() amended to
  *		  fix problem with trailing blanks.
  *
  *		o Update setValue() to support changes to the
  *		  OdbcStatement datetime routines.

  * 2002-05-20	Updated OdbcStatement.cpp
  *
  *		Contributed by Bernhard Schulte
  *		o Use TimeStamp instead of DateTime in setParameter().

  * 2002-05-20	Updated OdbcDateTime.cpp
  *
  *		Contributed by Bernhard Schulte
  *		- improvements to conversion routines to allow
  *      	  working with dates outside the range of 1900-2039
  *		o TimeStamp Struct to Timestamp
  *		o DateTime to Date Struct
  *		o TimeStamp to Timestamp Struct
  *		o ndate takes a new parameter - seconds,
  *		  because days won't fit in otherwise.

  * 2002-04-30	Updated main.cpp
  *
  *		Added suggestions from Carlos G. Alvarez
  *		o Test for logfile before trying to close it.
  *		o Changed parameter types for SQLSetConnectOption

  * 2002-04-30	Updated IscStatement.cpp
  *
  *		Added suggestions from LiWeimin
  *		o IscStatement::setValue
  *		  When writing a varchar decrement the sqllen by 2
  *		  before the test.
  *
  *		o IscStatement::getIscDate
  *		  Don't modify the date returned with this expression
  *		     / (24 * 60 * 60) + baseDate
  *		  just return the date.

  * 2002-04-30	Setup.cpp
  *
  *		Suggestion from Paul Schmidt
  *		Add role to Setup::configureDialog()


Finally, I must just add that I was having difficulties with my mail 
reader recently. This meant that I could'nt easily post to this list and 
had to do everything privately. I've got a new mail reader that works 
with my sourceforge id now, so hopefully we can keep everything out in 
the open and all can benefit from discussions about changes.


Paul
-- 

Paul Reeves
http://www.ibphoenix.com
Supporting users of Firebird and InterBase

[Firebird-odbc-devel] Re: Blob fields: wrong behaviour - fixed

[<sc...@de...>]

> I fixed wrong blob fields behaviour (tested with VCL 50 and Crystal
> Reports 8.5). Where do I post changes?
> 
> --
> Best regards
> 
> Robert Milharcic
> 
> ib-CADdy d.o.o. / www.ib-caddy.si
> 
> 
Hi,

I also made some changes conceerning the date and time values.
Until now it was impossible to store and/or get date values <'1.1.1901'  a=
nd 
>'1.1.2039' (a few days more or less).
So I 'misused' the TimeStamp-structure to store the real date in timestamp=
.date
and the seconds (not yust the nanos) in timestamp.nanos....
I also included the changes submitted by Carlos Guzm=E1n =C1lvarez.
Still i have those bugs in using blob-fields.
I would send the hole code to anyone who wants to have it (in a zip'd file=
).
If you  would send me the fixes about the blobs , I would by quite happy.
 -- please send your email also to 'sc...@de...' --

------------
   Best regards 

   Bernhard Schulte
------------	

[Firebird-odbc-devel] Blob fields: wrong behaviour - fixed

[Robert <rob...@ib...>]

I fixed wrong blob fields behaviour (tested with VCL 50 and Crystal
Reports 8.5). Where do I post changes?

--
Best regards

Robert Milharcic

ib-CADdy d.o.o. / www.ib-caddy.si

[Firebird-odbc-devel] chars are too long ?

[B. S. <sc...@de...>]

I used the latest drivers downloaded from ibphoenix.com,
built an application with BDE.
Took my favorite "test-table" with a field of "CHAR(10)" but in my 
dalphi-Application this field is shown as "CHAR(11)",  
TQuery.size=11 and TQuery.display size=11.
You can find the same behaviour, when connecting to this Database 
(by this DSN) with MS-Visual-Foxpro..
-->
I tried to correct the odbc-driver but don't really know where to begin 
(which function/method).
Maybe someone can give me a hint.

	Bernhard

Re-2: [Firebird-odbc-devel] Blob fields: wrong behaviour

[<woe...@ml...>]

Hello Paul,

first I want to apologize for my non-working modifications. Since I only have a MSVC 5 Personal Edition which refuses to compile the sources because of statically linked MFC, I did not and still do not have any possibility to test my changes. I already received feedback from one who had the same problem, but we could not solve it. Sorry that I did not inform you at once that there is a compiler error in my changes - I thought you were the ODBC driver developer and can handle that.

So for now I already have tried to "organize" a Pro compiler edition to be able to test my changes before submission - maybe I get one in a few days, and then I hopefully can solve the problem and test the driver. Hence I would like to suggest that someone maybe should make the ODBC driver dynamically linked to MSVC - if this is possible with little effort - so that it can be compiled with the Personal editions of Microsoft's compilers. 

Regards,
  Michael Woecherl

Original Message       processed by Tobit InfoCenter 
Subject: Re: [Firebird-odbc-devel] Blob fields: wrong behaviour (01-Mai-2002 16:19)
From:    pr...@ib...
To:      woe...@ml... (and 1 other)


On 23 Apr 2002 11:00:30 UT, woe...@ml... wrote:
>

> It would be great if somebody (of IBPhoenix?) could commit my
> changes into  cvs and make Win32 binaries available for download.
>


I've been going through your bug fix and I've found that it doesn't compile. The error appears to be associated with these two lines:


OdbcStatement::setValue (line 435)

  strcpy ((char*) binding->pointer, string[binding->blobCounter]);


OdbcStatement::setValue (line 440)

  memcpy (binding->pointer, string[binding->blobCounter], len);


The compiler wont accept them without a type cast. So far I've tried this kind of cast:


  (const char *) string[binding->blobCounter]


which the compiler accepts. Unfortunately a run-time access violation is then generated.


If you have any suggestions I'm happy to try them. I'm not the developer of the driver - just the maintainer of the source.



Paul

--

Paul Reeves

http://www.ibphoenix.com

Supporting users of Firebird and InterBase

To: pr...@ib...
    fir...@li...

RE: [Firebird-odbc-devel] Blob fields: wrong behaviour

[Pier A. G. <pgu...@an...>]

Hi Paul,

I modified lines 417 and 422 in this way:

line 417
strcpy ((char*) binding->pointer,string+binding->blobCounter);

line 422
memcpy (binding->pointer, string+binding->blobCounter, len);

Michael told me to modify also line 423 in this way:

((char*) (binding->pointer)) [len + 1] = 0;

The compiler accepted them. I rebuilt all but the driver didn't work.
Maybe I haven't used the latest source. I wasn't able to download them from
CVS (how can I do that with WinCVS?), and so I used those available for
download on the IBPhoenix site.

Regards,

Ing. Pier Alberto GUIDOTTI
ANALYSIS s.r.l.
Via Zanardi 403/23B
40131 BOLOGNA (ITALY)
http://www.analysisbo.it

Re: [Firebird-odbc-devel] Blob fields: wrong behaviour

[Paul R. <pr...@ib...>]

<HTML><HEAD>
<BASEFONT FACE=3D"Courier New" SIZE=3D"2" COLOR=3D"#000000">
</HEAD>
<BODY>
<div>On 23 Apr 2002 11:00:30 UT, woe...@ml...=
 wrote:<br>
&gt;<br></div>
<div><FONT COLOR=3D"#000080">&gt;&nbsp;It would be great if=
 somebody (of IBPhoenix?) could commit my</FONT><br>
<FONT COLOR=3D"#000080">&gt;&nbsp;changes into &nbsp;cvs and make=
 Win32 binaries available for download.</FONT><br>
<FONT COLOR=3D"#000080">&gt;</FONT><br>
<br></div>
<div>I've been going through your bug fix and I've found that it=
 doesn't compile. The error appears to be associated with these=
 two lines:<br></div>
<div>&nbsp;</div>
<div>OdbcStatement::setValue (line 435)<br></div>
<div>&nbsp; strcpy ((char*) binding-&gt;pointer,=
 string[binding-&gt;blobCounter]);<br></div>
<div><br>
OdbcStatement::setValue (line 440)<br></div>
<div>&nbsp; memcpy (binding-&gt;pointer,=
 string[binding-&gt;blobCounter], len);<br></div>
<div>&nbsp;</div>
<div>The compiler wont accept them without a type cast. So far=
 I've tried this kind of cast:<br></div>
<div>&nbsp;</div>
<div>&nbsp; (const char *)=
 string[binding-&gt;blobCounter]<br></div>
<div>&nbsp;</div>
<div>which the compiler accepts. Unfortunately a run-time access=
 violation is then generated.<br></div>
<div>&nbsp;</div>
<div>If you have any suggestions I'm happy to try them. I'm not=
 the developer of the driver - just the maintainer of the=
 source.<br></div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>Paul<br></div>
<div>--<br></div>
<div>Paul Reeves<br></div>
<div><a=
 href=3D"http://www.ibphoenix.com">http://www.ibphoenix.com</a><br>=
</div>
<div>Supporting users of Firebird and InterBase<br></div>
</body></html>

R: [Firebird-odbc-devel] bug in resolving Timestamp, problem in NUMERIC format

[Ferrari A. <fer...@ds...>]

Thanks for the response,
I'm using interclient too, without problems up to now, also for Numeric =
fields. I think because i don't use store procedures.
To compile ODBC-JDBC i used Microsoft Visual C++ easily, if you have =
this product and you want compile the source, you must download the cvs =
files, (If you can't i'll send them to you) the SDK for =
Interbase/Firebird and setting properly the Linking and C++ properties.
Currently i leaved ODBC-JDBC driver and i'm looking at =
http://ofbodbc.sourceforge.net/=20
It is another open source driver, and for my need it seems working fine.
=20
Best Regards,
Alberto Ferrari

-----Messaggio originale-----
Da: Siavcom Software S. de R.L. de C.V. [mailto:si...@ax...]
Inviato: luned=EC 29 aprile 2002 22.35
A: Ferrari Alberto; fir...@li...
Oggetto: Re: [Firebird-odbc-devel] bug in resolving Timestamp, problem =
in NUMERIC format


Recently I have working with JDBC and the last version (2.1) of =
Interclient for Firebird. I found some errors using Numeric and Decimal =
Fields=20
In java with JDBC and Interclient when a select or store procedure =
return a Decimal or Numerical Field with one or more decimal Interclient =
return the next error=20
=20
Error: [interclient] Unsupported feature: Using a JDBC 2 method which is =
not yet supported.
See API reference for exception =
interbase.interbclient.DriverNotCaptableException
[SQLCode: 7], [SQLState: 0A000]
=20
The Firebird-odbc JDBC I undertand use JDBC, I almost sure that many =
problem using Numeric or Decimals Fields come from JDBC
The solution is to chage all fields numeric or decimal to float or =
doubble precision but There are one problem more :
                       When you use a Float o double precision Field, =
JDBC lost decimasl. Maximun you can use 3 precision decimals if you need =
more precision
                       Is not the answer.
=20
=20
I readed many mail where many people found bugs in ODBC-JDBC but this =
Bugs an solutions never had been updated in CVS tree.
=20
If Firebird is not interested in update the new bug fixed I=B4m propose =
create a new Open Source ODBC-JDBC in sourceforce with other name, where =
the community can development and upgrade the new changes=20
=20
Who can help me how can I dowload the ODBC-JDBC and make exe file.
=20
=20
I=B4m developer software. I=B4m using Visual FoxPro and firebid. I use =
Easy Soft ODBC but I found that Easy Soft ODBC use the client of =
Interbase.
The client of Interbase use a lot of trasmision ( all data schema are =
trasmited on each  table or store procedure are consulted ) this cause a =
lot of trafic over the Net. If the client is in a LAN (Local Area =
Network) is not a big problem but if the client is outside of the LAN ( =
using Interent, DS0 ect) the connexion is slow.
=20
I made test using ODBC-JDBC in the past but when I tried to make a =
connection I had a fatal error an my aplication is closed.
=20
I Belive using ODBC-JDBC is the best solution of ODBC but we need the =
colaboration of all yours in making test and found and fix bugs.
=20
=20
=20
Thanks
=20
Eng. Fernando Cuadras
General Manager Siavcom Software=20
www.siavcom.com.mx
si...@ax...
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20

=20
----- Original Message -----=20
From: Ferrari  <mailto:fer...@ds...> Alberto=20
To: fir...@li...=20
Sent: Monday, April 29, 2002 2:22 AM
Subject: [Firebird-odbc-devel] bug in resolving Timestamp, problem in =
NUMERIC format


I all,

I don't know if there is a bug in resolving Timestamp, but I have an =
exception when i try to get a column of this type

I looked the code,  and i have found that if i comment these lines

if ((days > 24855) || (days < -24885))
                    throw SQLEXCEPTION (CONVERSION_ERROR, "date out of =
range");
at IscStatement::setValue(Value *value, XSQLVAR *var)

the driver works, but I have some problem in TIME format (the resulted =
format is not corrected in TIMESTAMP and in TIME).

I have a problem also for NUMERIC, it seems that the resulted metada is =
not correct, it seems to be a Integer not a Numeric.

Any suggestion??

Best regards,
Alberto Ferrari


_______________________________________________
Firebird-odbc-devel mailing list
Fir...@li...
https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel

Re: [Firebird-odbc-devel] bug in resolving Timestamp, problem in NUMERIC format

[Siavcom S. S. de R.L. de C.V. <si...@ax...>]

Recently I have working with JDBC and the last version (2.1) of =
Interclient for Firebird. I found some errors using Numeric and Decimal =
Fields=20
In java with JDBC and Interclient when a select or store procedure =
return a Decimal or Numerical Field with one or more decimal Interclient =
return the next error=20

Error: [interclient] Unsupported feature: Using a JDBC 2 method which is =
not yet supported.
See API reference for exception =
interbase.interbclient.DriverNotCaptableException
[SQLCode: 7], [SQLState: 0A000]

The Firebird-odbc JDBC I undertand use JDBC, I almost sure that many =
problem using Numeric or Decimals Fields come from JDBC
The solution is to chage all fields numeric or decimal to float or =
doubble precision but There are one problem more :
                       When you use a Float o double precision Field, =
JDBC lost decimasl. Maximun you can use 3 precision decimals if you need =
more precision
                       Is not the answer.


I readed many mail where many people found bugs in ODBC-JDBC but this =
Bugs an solutions never had been updated in CVS tree.

If Firebird is not interested in update the new bug fixed I=B4m propose =
create a new Open Source ODBC-JDBC in sourceforce with other name, where =
the community can development and upgrade the new changes=20

Who can help me how can I dowload the ODBC-JDBC and make exe file.


I=B4m developer software. I=B4m using Visual FoxPro and firebid. I use =
Easy Soft ODBC but I found that Easy Soft ODBC use the client of =
Interbase.
The client of Interbase use a lot of trasmision ( all data schema are =
trasmited on each  table or store procedure are consulted ) this cause a =
lot of trafic over the Net. If the client is in a LAN (Local Area =
Network) is not a big problem but if the client is outside of the LAN ( =
using Interent, DS0 ect) the connexion is slow.

I made test using ODBC-JDBC in the past but when I tried to make a =
connection I had a fatal error an my aplication is closed.

I Belive using ODBC-JDBC is the best solution of ODBC but we need the =
colaboration of all yours in making test and found and fix bugs.



Thanks

Eng. Fernando Cuadras
General Manager Siavcom Software=20
www.siavcom.com.mx
si...@ax...














  ----- Original Message -----=20
  From: Ferrari Alberto=20
  To: fir...@li...=20
  Sent: Monday, April 29, 2002 2:22 AM
  Subject: [Firebird-odbc-devel] bug in resolving Timestamp, problem in =
NUMERIC format


  I all,

  I don't know if there is a bug in resolving Timestamp, but I have an =
exception when i try to get a column of this type

  I looked the code,  and i have found that if i comment these lines

  if ((days > 24855) || (days < -24885))
                      throw SQLEXCEPTION (CONVERSION_ERROR, "date out of =
range");
  at IscStatement::setValue(Value *value, XSQLVAR *var)

  the driver works, but I have some problem in TIME format (the resulted =
format is not corrected in TIMESTAMP and in TIME).

  I have a problem also for NUMERIC, it seems that the resulted metada =
is not correct, it seems to be a Integer not a Numeric.

  Any suggestion??

  Best regards,
  Alberto Ferrari


  _______________________________________________
  Firebird-odbc-devel mailing list
  Fir...@li...
  https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel

[Firebird-odbc-devel] BUGS

[Carlos G.A. <car...@ho...>]

Hello:

I´m working with the driver since a week ago and i found some errors, at 
this moment i have only a problem within fix with the update of the BLOB 
fields, the other errors that i have encountered are explained in this mail.


Best Regards
Carlos Guzmán Álvarez

P.D.: Sorry about my bad English but i´m Spanish.



Main.cpp:

1.- In the SQLDisconnect function the block:

#ifdef LOGGING
	fclose (logFile);
#endif

should be:

#ifdef LOGGING
	if ( logFile )
		fclose (logFile);
#endif


2.- The SQLSetConnectOption don´t work the problem is inthe parameters type 
it should be:

RETCODE SQL_API SQLSetConnectOption  (HDBC arg0,
		 SQLUSMALLINT arg1,
		 SQLUINTEGER arg2)
{
	TRACE ("SQLSetConnectOption");

	return SQLSetConnectAttr (arg0, arg1, (SQLPOINTER *)arg2, 0);
}


OdbcStatement.cpp

1.- The OdbcStatement::setParameter method don´t wotk good with SQL_C_CHAR 
parameters that aren´t null terminated strings
I fixed it adding a new method to the PreparedStatement class and 
implementingg it in the IscPreparedStatement and IscCallableStatement 
classes, this new method can pass the length of the string:


....
switch(binding->sqlType)
{
	case SQL_CHAR:
	case SQL_VARCHAR:
	{
		/*
		* binding->precision is a new property of the class Binding
		*/
		statement->setString (parameter, (char*) binding->pointer, 
binding->precision);
	}
	break;
}
....



Sqlda.cpp:

1.- Sqlda::allocbuffer makes that the data returned by a SQLStatement was 
incorrect and that SQLColAttributes returned bad results for 
SQL_COLUMN_LENGTH. SQL_COLUMN_DISPLAY_SIZE, ..., i fixed this commenting 
this line:

var->sqllen = length;

With this line commented it´s neccesary other change in:

IscStatement.cpp

In the method IscStatement::setValue:

....

case SQL_TEXT:
{
	char *data = (char*) var->sqldata;
	data [var->sqllen] = 0;
	value->setString (data, false);
}
break;


IscStatement.cpp

1.- The getIscDate method of the class IscStatement should be: ( this error 
already has been posted in a past message )

ISC_DATE IscStatement::getIscDate(DateTime value)
{
	return value.date;
}


IscIndexInfoResultSet.cpp

1.- The method IscIndexInfoResultSet::getIndexInfo is incorrect it should 
be:

void IscIndexInfoResultSet::getIndexInfo(const char * catalog,
							 const char * schemaPattern,
							 const char * tableNamePattern,
							 bool unique, bool approximate)
{
	const char *v6 =
		"select NULL as table_cat,\n"							// 1
				"\tNULL as table_schem,\n"					// 2
				"\tidx.rdb$relation_name as table_name,\n"		// 3
				"\tidx.rdb$unique_flag as non_unique,\n"			// 4
				"\tNULL as index_qualifier,\n"				// 5
				"\tidx.rdb$index_name as index_name,\n"			// 6
				"\t(3) as \"TYPE\",\n"						// 7 (SQL_INDEX_OTHER)
				"\tseg.rdb$field_position as ordinal_position,\n" 	// 8
				"\tseg.rdb$field_name as column_name,\n"			// 9
				"\tidx.rdb$index_type as asc_or_desc,\n"			// 10
				"\tidx.rdb$statistics as cardinality,\n"			// 11
				"\tNULL as \"PAGES\",\n"					// 12
				"\tNULL as filter_condition\n"				// 13
		"from rdb$indices idx, rdb$index_segments seg\n"
		" where idx.rdb$index_name = seg.rdb$index_name\n";

	const char *preV6 =
		"select NULL as table_cat,\n"							// 1
				"\tNULL as table_schem,\n"					// 2
				"\tidx.rdb$relation_name as table_name,\n"		// 3
				"\tidx.rdb$unique_flag as non_unique,\n"	    		// 4
				"\tNULL as index_qualifier,\n"				// 5
				"\tidx.rdb$index_name as index_name,\n"			// 6
				"\t(3) as odbc_type,\n"						// 7 (SQL_INDEX_OTHER)
				"\tseg.rdb$field_position as ordinal_position,\n" 	// 8
				"\tseg.rdb$field_name as column_name,\n"		  	// 9
				"\tidx.rdb$index_type as asc_or_desc,\n"		  	// 10
				"\tidx.rdb$statistics as cardinality,\n"		  	// 11
				"\tNULL as odbc_pages,\n"					// 12
				"\tNULL as filter_condition\n"				// 13
		"from rdb$indices idx, rdb$index_segments seg\n"
		" where idx.rdb$index_name = seg.rdb$index_name\n";

	JString sql = (metaData->storesMixedCaseQuotedIdentifiers()) ? v6 : preV6;

	if (tableNamePattern)
		sql += expandPattern (" and idx.rdb$relation_name %s '%s'\n", 
tableNamePattern);

	if (unique)
		sql += " and idx.rdb$unique_flag = 1";

	sql += " order by idx.rdb$relation_name, idx.rdb$unique_flag, 
idx.rdb$index_name, seg.rdb$field_position";
	prepareStatement (sql);
	numberColumns = 13;
}


IscPrimaryKeysResultSet.cpp


1.- The method IscPrimaryKeysResultSet::getPrimaryKeys is incorrect it 
should be:

void IscPrimaryKeysResultSet::getPrimaryKeys(const char * catalog, const 
char * schemaPattern, const char * tableNamePattern)
{
	JString sql =
		"select NULL as table_cat,\n"						// 1
				"\tNULL as table_schem,\n"				// 2
				"\trel.rdb$relation_name as table_name,\n"	// 3
				"\tseg.rdb$field_name as column_name,\n"		// 4
				"\tseg.rdb$field_position as key_seq,\n"		// 5
				"\tidx.rdb$index_name as pk_name\n"			// 6
		"from rdb$relation_constraints rel, rdb$indices idx, rdb$index_segments 
seg\n"
		" where rel.rdb$constraint_type = 'PRIMARY KEY'\n"
		" and rel.rdb$index_name = idx.rdb$index_name\n"
		" and idx.rdb$index_name = seg.rdb$index_name\n";

	if (tableNamePattern)
		sql += expandPattern (" and rel.rdb$relation_name %s '%s'", 
tableNamePattern);

	sql += " order by rel.rdb$relation_name, idx.rdb$index_name, 
seg.rdb$field_position";
	prepareStatement (sql);
	numberColumns = 6;
}


IscProcedureColumnsResultSet.cpp


1.- The method IscProcedureColumnsResultSet::getProcedureColumns is 
incorrect it should be:

void IscProcedureColumnsResultSet::getProcedureColumns(const char * catalog,
													   const char * schemaPattern,
													   const char * procedureNamePattern,
													   const char * columnNamePattern)
{
	JString sql =
		"select NULL as table_cat,\n"							// 1
				"\tNULL as table_schem,\n"					// 2
				"\tpp.rdb$procedure_name as procedure_name,\n"		// 3
				"\tpp.rdb$parameter_name as column_name,\n"		// 4
				"\tpp.rdb$parameter_type as column_type,\n"		// 5
				"\tpp.rdb$field_type as data_type,\n"			// 5 + 1
				"\tpp.rdb$field_sub_type as type_name,\n"			// 6 + 1
				"\tpp.rdb$field_length as column_size,\n"			// 7 + 1
				"\tnull as buffer_length,\n"					// 8 + 1
				"\tf.rdb$field_scale as decimal_digits,\n"		// 9 + 1
				"\t10 as num_prec_radix,\n"					// 10 + 1
				"\tf.rdb$null_flag as nullable,\n"				// 11 + 1
				"\tf.rdb$description as remarks,\n"				// 12 + 1
				"\tf.rdb$default_value as column_def,\n"			// 13 + 1
				"\tnull as SQL_DATA_TYPE,\n"					// 14 + 1
				"\tnull as SQL_DATETIME_SUB,\n"				// 15 + 1
				"\tf.rdb$field_length as CHAR_OCTET_LENGTH,\n"		// 16 + 1
				"\tpp.rdb$parameter_number as ordinal_position,\n"	// 17 + 1
				"\t'YES' as IS_NULLABLE\n"					// 18 + 1
		"from rdb$procedure_parameters pp, rdb$fields f\n"
		"where pp.rdb$field_source = f.rdb$field_name";

	if (procedureNamePattern)
		sql += expandPattern (" and pp.rdb$procedure_name %s '%s'", 
procedureNamePattern);

	if (columnNamePattern)
		sql += expandPattern (" and pp.rdb$parameter_name %s '%s'", 
columnNamePattern);

	sql += " order by pp.rdb$procedure_name, pp.rdb$parameter_number";
	prepareStatement (sql);
	numberColumns = 19;
}



_________________________________________________________________
Envíe y reciba su correo de Hotmail desde el móvil: http://mobile.msn.com

[Firebird-odbc-devel] bug in resolving Timestamp, problem in NUMERIC format

[Ferrari A. <fer...@ds...>]

I all,

I don't know if there is a bug in resolving Timestamp, but I have an =
exception when i try to get a column of this type

I looked the code,  and i have found that if i comment these lines

if ((days > 24855) || (days < -24885))
                    throw SQLEXCEPTION (CONVERSION_ERROR, "date out of =
range");
at IscStatement::setValue(Value *value, XSQLVAR *var)

the driver works, but I have some problem in TIME format (the resulted =
format is not corrected in TIMESTAMP and in TIME).

I have a problem also for NUMERIC, it seems that the resulted metada is =
not correct, it seems to be a Integer not a Numeric.

Any suggestion??

Best regards,
Alberto Ferrari
			=09

[Firebird-odbc-devel] Interbase+ASP+ADO

[Atif T. <at...@ad...>]

hello,

can any body let me know how to connect Interbase from ASP using ADO.

regards

[Firebird-odbc-devel] Bug with text blob fields larger than 1024 bytes

[Pier A. G. <pgu...@an...>]

Using Crystal Reports 8.5 I noted that when a text blob field is larger than
1024 bytes, the first block of 1024 bytes is repeated two or more times.
Maybe this is the same bug reported by Michael Woecherl.

Ing. Pier Alberto GUIDOTTI
ANALYSIS s.r.l.
Via Zanardi 403/23B
40131 BOLOGNA (ITALY)
http://www.analysisbo.it

[Firebird-odbc-devel] ERROR WITH TIMESTAMP IN VB

[Ferrari A. <fer...@ds...>]

I all,

I'm using ODBCJDBC with Visual Basic (ADO 2.6 sp2) :-( ..
when i try to read a timestamp i get this error: "run time error =
-2137217887(800040e21)". It seems, by debugging, that the driver sees =
the rigth DataType ( Timestamp) but with a actual size of 16 bytes, .. =
so i suspect that the Timestamp's size read is greater than that =
expected.

any suggest or workaround ???

Best Regards,
Alberto Ferrari.

Re: [Firebird-odbc-devel] Blob fields: wrong behaviour

[Paul R. <pr...@ib...>]

On 23 Apr 2002 11:00:30 UT, woe...@ml... wrote:
>=A0It would be great if somebody (of IBPhoenix?) could commit my
>=A0changes into =A0cvs and make Win32 binaries available for=
 download.
>
>
>=A0Attached files: OdbcStatment.cpp =A0 =A0 =A0 -- my changed version
>=A0dbcStatment.h =A0 =A0 =A0 =A0 -- my changed =A0version
>
>=A0dbcStatment.cpp.diff =A0-- diff cvs source : my version
>=A0dbcStatment.h.diff =A0 =A0-- diff cvs source : my version I=
 downloaded
>=A0cvs sources on March 15, 2002 (ok, that's centuries ago...).
>

It is not centuries ago in terms of the ODBC driver. I don't=
 believe any changes have been committed since then. There are a=
 couple in the pipeline, and now yours.

If all goes well, I will actually get this weeks work done this=
 week, and be able to spend some time next week bringing the=
 driver up to date and testing the changes. It would certainly be=
 nice to get a new release out.


Paul
--
Paul Reeves
http://www.ibphoenix.com
Supporting users of Firebird and InterBase

[Firebird-odbc-devel] {ts}

[Paul S. <pa...@tr...>]

Dear List:

Crystal Reports has a nasty habit of when dealing with dates and 
times using the syntax 

DATETIME_FIELD = {ts('2002-02-02 01:00:02)}

most of the drivers don't handle this, including the ODBCJDBC 
driver, anyone know if there is a way of turning this off?  Or maybe 
handling this easily?

Paul
Paul Schmidt, President
Tricat Technologies
pa...@tr...
www.tricattechnologies.com

Re: [Firebird-odbc-devel] A bug in IBPhoenix ODBC Driver

[LiWeimin <li...@37...>]

Another bug:
   case SQL_VARYING:
    {
    int length = *((short*) var->sqldata) ;
    char *data = var->sqldata + 2;
    if (length < var->sqllen-2)

""LiWeimin"" <li...@37...> wrote in message
news:a90u8p$di9$1...@ne......
> ISC_DATE IscStatement::getIscDate(DateTime value)
> {
>  return value.date / (24 * 60 * 60) + baseDate;
> }
>
>
> just to be :
>
> ISC_DATE IscStatement::getIscDate(DateTime value)
> {
>  return value.date;
>
> }
>
> Another thing:
>
> I meet error when I do this:
>
>  m_pSet->Open();
>  while ( !m_pSet->IsEOF() ) {
>   SelectAnotherTable(m_pSet->m_COL);
>   m_pSet->MoveNext();
>  }
>
>
>
>
>
>
> _______________________________________________
> Firebird-odbc-devel mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>

[Firebird-odbc-devel] TWO ODBC driver BUGS

[Pier A. G. <pgu...@an...>]

I discovered two bugs:

1) If a BLOB field contains a graphic larger than 1Kb, the application
crashes with a Runtime error.

2) If a time stamp field contains an "impossible" date (like 0200/1/1 or
9900/1/1), the application crashes with a runtime error.

I reproduced those bugs with both Crystal 8.5 and dBASE (dB2K).

Regards,

Ing. Pier Alberto GUIDOTTI
ANALYSIS s.r.l.
Via Zanardi 403/23B
40131 BOLOGNA (ITALY)
http://www.analysisbo.it

[Firebird-odbc-devel] A bug in IBPhoenix ODBC Driver

[LiWeimin <li...@37...>]

ISC_DATE IscStatement::getIscDate(DateTime value)
{
 return value.date / (24 * 60 * 60) + baseDate;
}


just to be :

ISC_DATE IscStatement::getIscDate(DateTime value)
{
 return value.date;

}

Another thing:

I meet error when I do this:

 m_pSet->Open();
 while ( !m_pSet->IsEOF() ) {
  SelectAnotherTable(m_pSet->m_COL);
  m_pSet->MoveNext();
 }

[Firebird-odbc-devel] .NET Provider?

[Niels B (Developmentor) <ni...@de...>]

I apologize for the x-post, but at this stage I really didn't know which 
group to post to.

Anyway, has there been any discussions about a provider for MS .NET 
framework? I have tried to look through the psots but haven't found 
anything.

Would there be interest in development of that kind of provider?

Niels

-- 
***************************************
* Niels Berglund
* Developmentor
* ni...@de...
* http://staff.develop.com/nielsb/
***************************************

[Firebird-odbc-devel] Bug report: FirebirdSS-1.0.0-796 depends on localhost in /etc/hosts.equiv

[Mark B. <bu...@mi...>]

Bug report: FirebirdSS-1.0.0-796 depends on having localhost in
/etc/hosts.equiv

Redhat 7.x installs "localhost.localdomain" in /etc/hosts.equiv.  If this
bogus alias is removed from /etc/hosts without correcting /etc/hosts.equiv
to match (something not exactly obvious), an error is reported for new local
connections in interbase.log

[Firebird-odbc-devel] Bug report: RPM package isc_config permissions problem

[Mark B. <bu...@mi...>]

The FirebirdSS-1.0.0.796 rpm package installs /opt/interbase/isc_config as
rw-r----- (chmod 540).

The isql utility attempts to read this file on startup, but cannot, because
it is not world-readable, which results in an error in interbase.log.

Re: [Firebird-odbc-devel] I found a bug - and a fix for it too.

[Paul R. <pr...@ib...>]

[repost - I still forget to use the Reply-all button sometimes]

Paul Schmidt wrote:
> 
> 
> Then the configuration dialog will display the current role, and update the role
> setting in the registry.  I only have read access to the CVS tree, so if someone who
> has write access, wants I can send them my copy of setup.cpp to update the tree.

Send it to me and I'll take a look at it.
 
> If anyone has comments on this then please let me know....
> 

Will do.

> BTW how do you get write access to the tree, using WinCVS?
> 

You need to be a member of the Firebird project. Membership gives full
write access to the whole CVS tree, not just the sub-projects. For that
reason prospective members are asked to contribute to the code base
with some patches that get accepted before they can become members. So
you've made a start. 


Paul 
-- 

Paul Reeves
http://www.ibphoenix.com
Supporting users of Firebird and InterBase

RE: [Firebird-odbc-devel] I found a bug - and a fix for it too.

[Dmitry Y. <di...@us...>]

Hi Paul,

> Okay, so it's more a PITA then a real bug, In OdbcJdbcSetup, in
> Setup::configureDialog()   two lines are missing.
>
> Add ~248 	dialog.m_role = role;
> Add ~258         role = dialog.m_role;
>
> Then the configuration dialog will display the current role,
> and update the role
> setting in the registry.  I only have read access to the CVS
> tree, so if someone who
> has write access, wants I can send them my copy of setup.cpp
> to update the tree.

It could be probably me, if others don't mind.

> BTW how do you get write access to the tree, using WinCVS?

If you want to become an actual developer and contribute to the project, you
should ask one of the Firebird admins to get CVS commit rights. Then I could
guide you through the steps required to set up WinCVS properly. Yes, I
remember what I promised you privately a couple of weeks ago, but I was a
kind of busy lately. It seems now it's time to rehabilitate myself ;-)

BTW, have you succeeded in solving your problems with Crystal?


Dmitry

[Firebird-odbc-devel] I found a bug - and a fix for it too.

[Paul S. <pa...@tr...>]

Okay, so it's more a PITA then a real bug, In OdbcJdbcSetup, in 
Setup::configureDialog()   two lines are missing.

Add ~248 	dialog.m_role = role;
Add ~258         role = dialog.m_role;

Then the configuration dialog will display the current role, and update the role 
setting in the registry.  I only have read access to the CVS tree, so if someone who 
has write access, wants I can send them my copy of setup.cpp to update the tree.

If anyone has comments on this then please let me know....

BTW how do you get write access to the tree, using WinCVS?

Paul
Paul Schmidt
Tricat Technologies
pa...@tr...
www.tricattechnologies.com