You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(23) |
Sep
(6) |
Oct
(2) |
Nov
(2) |
Dec
(5) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
|
Feb
(14) |
Mar
(16) |
Apr
(14) |
May
(25) |
Jun
(38) |
Jul
(22) |
Aug
(39) |
Sep
(3) |
Oct
(13) |
Nov
(47) |
Dec
(3) |
2003 |
Jan
(38) |
Feb
(39) |
Mar
(24) |
Apr
(57) |
May
(30) |
Jun
|
Jul
(39) |
Aug
(90) |
Sep
(41) |
Oct
(141) |
Nov
(158) |
Dec
(137) |
2004 |
Jan
(86) |
Feb
(169) |
Mar
(100) |
Apr
(83) |
May
(94) |
Jun
(77) |
Jul
(85) |
Aug
(54) |
Sep
(45) |
Oct
(36) |
Nov
(42) |
Dec
(70) |
2005 |
Jan
(46) |
Feb
(44) |
Mar
(50) |
Apr
(73) |
May
(90) |
Jun
(87) |
Jul
(41) |
Aug
(47) |
Sep
(28) |
Oct
(23) |
Nov
(44) |
Dec
(81) |
2006 |
Jan
(21) |
Feb
(9) |
Mar
(82) |
Apr
(14) |
May
(109) |
Jun
(175) |
Jul
(188) |
Aug
(44) |
Sep
(5) |
Oct
(47) |
Nov
(15) |
Dec
(34) |
2007 |
Jan
(75) |
Feb
(24) |
Mar
(30) |
Apr
(4) |
May
(28) |
Jun
(9) |
Jul
(13) |
Aug
(13) |
Sep
(29) |
Oct
(15) |
Nov
(19) |
Dec
(12) |
2008 |
Jan
(7) |
Feb
(19) |
Mar
(1) |
Apr
(7) |
May
(13) |
Jun
(19) |
Jul
(17) |
Aug
(29) |
Sep
(15) |
Oct
(37) |
Nov
(18) |
Dec
(29) |
2009 |
Jan
(23) |
Feb
(12) |
Mar
(8) |
Apr
(16) |
May
(11) |
Jun
(1) |
Jul
(2) |
Aug
(1) |
Sep
|
Oct
(9) |
Nov
(17) |
Dec
(31) |
2010 |
Jan
(15) |
Feb
(5) |
Mar
(4) |
Apr
(8) |
May
(1) |
Jun
(5) |
Jul
(17) |
Aug
(2) |
Sep
(12) |
Oct
(33) |
Nov
(14) |
Dec
(24) |
2011 |
Jan
(11) |
Feb
(2) |
Mar
(34) |
Apr
(11) |
May
(12) |
Jun
(3) |
Jul
(6) |
Aug
(11) |
Sep
(10) |
Oct
(1) |
Nov
(8) |
Dec
|
2012 |
Jan
(16) |
Feb
(2) |
Mar
|
Apr
(2) |
May
(6) |
Jun
(2) |
Jul
(7) |
Aug
|
Sep
|
Oct
(7) |
Nov
(22) |
Dec
(2) |
2013 |
Jan
(1) |
Feb
(24) |
Mar
(15) |
Apr
(2) |
May
(3) |
Jun
|
Jul
(2) |
Aug
|
Sep
(2) |
Oct
(6) |
Nov
(10) |
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
(5) |
2015 |
Jan
(1) |
Feb
(4) |
Mar
(3) |
Apr
(3) |
May
|
Jun
(3) |
Jul
(1) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
2016 |
Jan
(1) |
Feb
(9) |
Mar
(4) |
Apr
|
May
(6) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(7) |
Nov
(13) |
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(12) |
Oct
(4) |
Nov
|
Dec
|
2018 |
Jan
(6) |
Feb
|
Mar
|
Apr
|
May
(6) |
Jun
|
Jul
(9) |
Aug
(4) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
2019 |
Jan
(1) |
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(3) |
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2025 |
Jan
|
Feb
(2) |
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Paul R. <pr...@ib...> - 2002-11-29 09:51:07
|
Ostash! wrote: > Hello All! > > I have some troubles with compilation under linux, but I did it. I > can post a patch done by me in order to make it work. Also I can > prepare makefiles for unixes for compiling odbc driver. > Please post them to the list if you can, or else send them to me. I'll commit them to the tree. > I have a question: is driver quite stable now in order to use it > in serious projects? What open bugs are konown now? > That is a good question. It rather depends upon where you are standing. The core part of the driver - executing sql statements and retrieving data - is sound. Very little extra work has been needed in that layer. The real problems have been around supporting the different versions of ODBC that exist. Each tool (such as Access, or Crystal Reports) is written to expect an ODBC driver to be compliant at a particular level and in a particular way. Some tools fall over if they encounter any kind of error. Other tools ignore the error if they can. Until Carlos Alvarez contributed numerous fixes to help the driver appear more compliant with these applications it was very difficult to see if there were errors in the underlying data access layer. For instance, now that we can use Access with the driver it appears that there is a problem with NUMERICs - Access mangles them completely. If I open the same table in the same database with Borlands BDE-based SQL Explorer (using the driver, of course) the numeric column is displayed correctly. However, under DBExplorer varchars don't seem to get truncated correctly. Under Access they do. So, the core data retrieval layer is sound, by the way many applications interact with it still has some problems. So, like I said - it depends on where you are standing. All I can recommend is that you test it against your data in your application. Paul -- Paul Reeves http://www.ibphoenix.com Supporting users of Firebird and InterBase |
From: Don L. <dl...@ep...> - 2002-11-28 21:06:44
|
Hello, I've downloaded the latest build and got it to work using MS Access. Unfortunately, I cannot insert a new row into a table. Usually there is a empty row add the end of the table when viewing it. There is none using this driver. |
From: Ostash! <os...@uk...> - 2002-11-28 19:58:23
|
Hello All! I have problems with ODBC driver under linux (via unixODBC). It works fine while I'm selecting, but when I try insert something into table I receive some strange messages. -----------------------------------------------------------------------= -- [ostash@linuxtest ostash]$ isql kpinet_fb sysdba masterkey -v >>[unixODBC][Driver Manager]Driver does not support the requested versi= on +---------------------------------------+ | Connected! | | | | sql-command | | help [tablename] | | quit | | | +---------------------------------------+ SQL> select * from flags; +------------+----------------------+ | ID_FLAG | FLAG | +------------+----------------------+ | 1 | connect | | 2 | connected | | 3 | disconnect | | 4 | disconnected | | 5 | adm_connect | | 6 | adm_connected | | 7 | adm_disconnect | | 8 | adm_disconnected | +------------+----------------------+ -1 rows affected SQL> insert into flags(id_flag) values(12) >>[unixODBC]current statement doesn't return results [ISQL]ERROR: Could not SQLPrepare SQL> -----------------------------------------------------------------------= -- Can anybody explain me what means messages in lines with two "greater" signs on the beginning? Best regards, Ostash! np: Vyachislav Butusov - Gibraltar =2E.. [Team Hot Sevastopol girls] [Team Ukrainian language] --- The Bat! 1.53d Windows NT 5.0.2195 Service Pack 2 * Origin: =F3=CF=C2=C1=CB=C1 =D3 =CD=C9=CC=C9=C3=C9=C5=CA =CF=C2=C5=DD= =C1=CC=C1 =D0=D2=C9=C4=D4=C9! (os...@uk...) |
From: Ostash! <os...@uk...> - 2002-11-27 18:37:38
|
Hello All! I have some troubles with compilation under linux, but I did it. I can post a patch done by me in order to make it work. Also I can prepare makefiles for unixes for compiling odbc driver. I have a question: is driver quite stable now in order to use it in serious projects? What open bugs are konown now? Best regards, Ostash! np: Scorpions - Always Somewhere =2E.. [Team Hot Sevastopol girls] [Team Ukrainian language] --- The Bat! 1.53d Windows NT 5.0.2195 Service Pack 2 * Origin: =F0=D2=CF=C7=D2=C1=CD=CD=D5 =C3=C9=CB=CC=CF=CD =CE=C5 =C9=D3= =D0=CF=D2=D4=C9=DB=D8 (os...@uk...) |
From: Thomas M. <tm...@bs...> - 2002-11-27 15:16:18
|
Thank you both for the extra effort. We do cross database development so we only you VARCHAR, NUMERIC, and TIMESTAMP. So far all of these seem to be working fine. If you have a small table ( < 100 records) with other data types and good test data, I will have my QC person check that the data in the table matches what is in the Crystal report. Paul Reeves wrote: > > I've refreshed the snapshot available for download here: > > http://www.ibphoenix.com/downloads/OdbcJdbc-Snapshot.zip > > It now incorporates the patches submitted by Carlos Alvarez on > 25-Nov-2002. > > It appears to fix the bug reported by Thomas Miller with > NUMERIC/DECIMAL values in the range 0.1 to 0.99. > > > Paul -- Thomas Miller Delphi Client/Server Certified Developer BSS Accounting & Distribution Software BSS Enterprise Accounting FrameWork http://www.bss-software.com |
From: Paul R. <pr...@ib...> - 2002-11-27 10:12:27
|
I've refreshed the snapshot available for download here: http://www.ibphoenix.com/downloads/OdbcJdbc-Snapshot.zip It now incorporates the patches submitted by Carlos Alvarez on 25-Nov-2002. It appears to fix the bug reported by Thomas Miller with NUMERIC/DECIMAL values in the range 0.1 to 0.99. Paul -- Paul Reeves http://www.ibphoenix.com Supporting users of Firebird and InterBase |
From: Thomas M. <tm...@bs...> - 2002-11-25 17:40:28
|
Problem still exists with the last download. Again, the only time we see the problem is with decimal only values with he first position being non zero. Looking forward to the continued testing of your fixes. PS: the data type for this column is NUMERIC(18,6); Thomas Miller wrote: > Could you test with the following values in the field: > > Value Value > in DB in Crystal > > 0.05 > 0.05 > 0.15 > 150,000 > 0.37 > 370,000 > 0.66 > 660,000 > 0.97 > 970,000 > 1.33 > 1.33 > > The 4 middle values have given me the wrong value back. > They have been integer multiplied by 6 decimal places. > > Carlos Guzmán Álvarez wrote: > -- Thomas Miller Delphi Client/Server Certified Developer BSS Accounting & Distribution Software BSS Enterprise Accounting FrameWork http://www.bss-software.com |
From: <car...@te...> - 2002-11-25 14:57:26
|
Hello: The patch for Sqlda.cpp allow to distingish between DECIMAL and NUMERIC fields. The patch for Value.cpp solve problems with Conversion from decimal and numeric fields to char ( these datatypes are mapped as SQL_C_CHAR on SqlBindCol function using Access ). Best regards Carlos Guzmán Álvarez Vigo-Spain |
From: Paul R. <pr...@ib...> - 2002-11-25 10:01:26
|
A newer snapshot is now available here: http://www.ibphoenix.com/downloads/OdbcJdbc-Snapshot.zip It incorporates the two patches submitted by Carlos Alvarez. Paul -- Paul Reeves http://www.ibphoenix.com Supporting users of Firebird and InterBase |
From: Thomas M. <tm...@bs...> - 2002-11-24 18:40:16
|
Could you test with the following values in the field: Value Value in DB in Crystal 0.05 > 0.05 0.15 > 150,000 0.37 > 370,000 0.66 > 660,000 0.97 > 970,000 1.33 > 1.33 The 4 middle values have given me the wrong value back. They have been integer multiplied by 6 decimal places. Carlos Guzmán Álvarez wrote: > Hello: > >> >> Thanks for this patch and the 'time' one. I've updated my local sources >> and done some limited testing. > > > :) > >> It doesn't appear to solve Thomas Miller's problem although it obviously >> makes it much easier to fix. > > > > I made some test with access and solve some problems, for example a > field numeric(9,3) was mapped, without the patch, on access, as > integer ( as i remember ), and gives bad values when you try to get > the data, with the patch the field is mapped well and the value > returned is correct, i don´t know if this is the same problem of > Thomas Miller's but all my other test gives correct results. > >> I don't have any more time today, but I'll put out a new snapshot on >> Monday and update the CVS tree at the same time. > > > > Ok :) > > > > > Best regards > Carlos Guzmán álvarez > Vigo-Spain > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Firebird-odbc-devel mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel > -- Thomas Miller Delphi Client/Server Certified Developer BSS Accounting & Distribution Software BSS Enterprise Accounting FrameWork http://www.bss-software.com |
From:
<car...@te...> - 2002-11-24 13:55:03
|
Hello: > > Thanks for this patch and the 'time' one. I've updated my local sources > and done some limited testing. :) > It doesn't appear to solve Thomas Miller's problem although it obviously > makes it much easier to fix. I made some test with access and solve some problems, for example a field numeric(9,3) was mapped, without the patch, on access, as integer ( as i remember ), and gives bad values when you try to get the data, with the patch the field is mapped well and the value returned is correct, i don´t know if this is the same problem of Thomas Miller's but all my other test gives correct results. > I don't have any more time today, but I'll put out a new snapshot on > Monday and update the CVS tree at the same time. Ok :) Best regards Carlos Guzmán álvarez Vigo-Spain |
From: Paul R. <pr...@ib...> - 2002-11-24 13:36:30
|
Carlos Guzm=E1n =C1lvarez wrote: > Hello: >=20 >=20 > This patch allow to numeric and decimal datatypes to be reported well o= n=20 > some catalog functions instead of as they are stored on firebird databa= ses. >=20 >=20 Thanks for this patch and the 'time' one. I've updated my local sources=20 and done some limited testing. It doesn't appear to solve Thomas Miller's problem although it obviously=20 makes it much easier to fix. I don't have any more time today, but I'll put out a new snapshot on=20 Monday and update the CVS tree at the same time. Paul --=20 Paul Reeves http://www.ibphoenix.com Supporting users of Firebird and InterBase |
From:
<car...@te...> - 2002-11-23 12:36:08
|
Hello: This patch allow to use Time fields on Access. Best Regards Carlos Guzmán Álvarez Vigo-Spain P.S.: Probably only with Value.cpp patch will be sufficient, but i don´t test it, but i think changes on OdbcStatement.cpp and Types.h can allow to get better handling of datetimes fields. |
From: mog_ur <mo...@ab...> - 2002-11-23 00:05:18
|
Hola Lo primero es q no se si se puede escribir en castellano en la lista, así q si hay algún problema decídmelo y procuraré hacerlo en Ingles. Mi pregunta es la siguiente: Estoy intentando acceder a FireBird desde VisualBasic y lo consigo pero con un rendimiento mucho menor que con Access y eso era justo lo contrario a lo q yo esperaba, no se si es por culpa del driver. Si alguien sabe como puedo mejorar el rendimiento de acceso a FireBird desde VisualBasic me ayudaría mucho ya q estoy un poco desesperado Gracias mog_ur |
From: Thomas M. <tm...@bs...> - 2002-11-22 23:05:48
|
That's great. If you can build it and send me the file, I will test it. I don't have anyway to build it. Carlos Guzmán Álvarez wrote: > Hello: > > > This patch allow to numeric and decimal datatypes to be reported well > on some catalog functions instead of as they are stored on firebird > databases. > > > > > Best regards > Carlos Guzmán Álvarez > Vigo-Spain > >------------------------------------------------------------------------ > >Index: IscColumnsResultSet.cpp >=================================================================== >RCS file: /cvsroot/firebird/OdbcJdbc/IscDbc/IscColumnsResultSet.cpp,v >retrieving revision 1.7 >diff -u -r1.7 IscColumnsResultSet.cpp >--- IscColumnsResultSet.cpp 21 Nov 2002 14:37:48 -0000 1.7 >+++ IscColumnsResultSet.cpp 22 Nov 2002 22:14:07 -0000 >@@ -124,17 +124,18 @@ > resultSet->setValue (17, resultSet->getInt (23)+1); // ORDINAL_POSITION > > //translate to the SQL type information >- int blrType = resultSet->getInt (5); // DATA_TYPE >- int subType = resultSet->getInt (6); // SUB_TYPE >- int length = resultSet->getInt (7); // COLUMN_SIZE >- int array = resultSet->getInt (21); // ARRAY_DIMENSION >+ int blrType = resultSet->getInt (5); // DATA_TYPE >+ int subType = resultSet->getInt (6); // SUB_TYPE >+ int length = resultSet->getInt (7); // COLUMN_SIZE >+ int scale = resultSet->getInt (9); // DECIMAL_DIGITS >+ int array = resultSet->getInt (21); // ARRAY_DIMENSION > int precision = resultSet->getInt (25); // COLUMN_PRECISION > > if (resultSet->valueWasNull) > array = 0; > > int dialect = resultSet->statement->connection->getDatabaseDialect(); >- IscSqlType sqlType (blrType, subType, length, length, dialect, precision); >+ IscSqlType sqlType (blrType, subType, length, length, dialect, precision, scale); > > JString type; > type.Format ("%s%s", (array) ? "ARRAY OF " : "", sqlType.typeName); >@@ -422,8 +423,8 @@ > switch (sqlType.type) > { > case JDBC_NUMERIC: >- case JDBC_DECIMAL: >- resultSet->setValue (9, resultSet->getInt(9)*-1); // Scale > 0 >+ case JDBC_DECIMAL: >+ resultSet->setValue (9, resultSet->getInt(9)*-1); // Scale > 0 > break; > case JDBC_CHAR: > case JDBC_VARCHAR: >@@ -482,5 +483,4 @@ > // Is Nullable - I'm seeing everything twice > > resultSet->setValue (18, ((resultSet->getInt (11)) == 0) ? "NO" : "YES"); >- > } > >------------------------------------------------------------------------ > >Index: IscProcedureColumnsResultSet.cpp >=================================================================== >RCS file: /cvsroot/firebird/OdbcJdbc/IscDbc/IscProcedureColumnsResultSet.cpp,v >retrieving revision 1.4 >diff -u -r1.4 IscProcedureColumnsResultSet.cpp >--- IscProcedureColumnsResultSet.cpp 11 Oct 2002 11:09:05 -0000 1.4 >+++ IscProcedureColumnsResultSet.cpp 22 Nov 2002 22:15:39 -0000 >@@ -123,12 +123,14 @@ > int type = (parameterType) ? SQL_PARAM_INPUT : SQL_PARAM_OUTPUT; > resultSet->setValue (5, type); > >- int blrType = resultSet->getInt (6); // field type >- int subType = resultSet->getInt (7); >- int length = resultSet->getInt (8); >- int dialect = resultSet->statement->connection->getDatabaseDialect(); >+ int blrType = resultSet->getInt (6); // field type >+ int subType = resultSet->getInt (7); >+ int length = resultSet->getInt (8); >+ int scale = resultSet->getInt (10); >+ int dialect = resultSet->statement->connection->getDatabaseDialect(); > int precision = resultSet->getInt (19); >- IscSqlType sqlType (blrType, subType, length, length, dialect, precision); >+ >+ IscSqlType sqlType (blrType, subType, length, length, dialect, precision, scale); > > resultSet->setValue (6, sqlType.type); > resultSet->setValue (7, sqlType.typeName); > >------------------------------------------------------------------------ > >Index: IscSpecialColumnsResultSet.cpp >=================================================================== >RCS file: /cvsroot/firebird/OdbcJdbc/IscDbc/IscSpecialColumnsResultSet.cpp,v >retrieving revision 1.2 >diff -u -r1.2 IscSpecialColumnsResultSet.cpp >--- IscSpecialColumnsResultSet.cpp 11 Oct 2002 11:09:06 -0000 1.2 >+++ IscSpecialColumnsResultSet.cpp 22 Nov 2002 22:14:56 -0000 >@@ -108,11 +108,12 @@ > //translate to the SQL type information > int blrType = resultSet->getInt (3); // field type > int subType = resultSet->getInt (4); >+ int scale = resultSet->getInt (12); > int length = resultSet->getInt (11); > int precision = resultSet->getInt (13); > > int dialect = resultSet->statement->connection->getDatabaseDialect(); >- IscSqlType sqlType (blrType, subType, length, length, dialect, precision); >+ IscSqlType sqlType (blrType, subType, length, length, dialect, precision, scale); > > char *type, t[50]; > type = t; >@@ -123,7 +124,7 @@ > > setCharLen (5, 6, sqlType); > >- int scale = resultSet->getInt(12)*-1; >+ scale = resultSet->getInt(12)*-1; > resultSet->setValue(7,scale); > > resultSet->setValue(8,1); > >------------------------------------------------------------------------ > >Index: IscSqlType.h >=================================================================== >RCS file: /cvsroot/firebird/OdbcJdbc/IscDbc/IscSqlType.h,v >retrieving revision 1.2 >diff -u -r1.2 IscSqlType.h >--- IscSqlType.h 11 Oct 2002 11:09:06 -0000 1.2 >+++ IscSqlType.h 22 Nov 2002 22:12:54 -0000 >@@ -32,8 +32,8 @@ > class IscSqlType > { > public: >- void getType (int blrType, int subType, int length, int bufferLen, int dialect, int precision); >- IscSqlType(int blrType, int subType, int length, int bufferLen, int dialect, int precision); >+ void getType (int blrType, int subType, int length, int bufferLen, int dialect, int precision, int scale); >+ IscSqlType(int blrType, int subType, int length, int bufferLen, int dialect, int precision, int scale); > virtual ~IscSqlType(); > > int type; > >------------------------------------------------------------------------ > >Index: IscSqlType.cpp >=================================================================== >RCS file: /cvsroot/firebird/OdbcJdbc/IscDbc/IscSqlType.cpp,v >retrieving revision 1.3 >diff -u -r1.3 IscSqlType.cpp >--- IscSqlType.cpp 22 Nov 2002 14:56:34 -0000 1.3 >+++ IscSqlType.cpp 22 Nov 2002 22:11:28 -0000 >@@ -34,6 +34,7 @@ > // IscSqlType.cpp: implementation of the IscSqlType class. > // > ////////////////////////////////////////////////////////////////////// >+#include <windows.h> > > #include "IscDbc.h" > #include "IscSqlType.h" >@@ -42,9 +43,9 @@ > // Construction/Destruction > ////////////////////////////////////////////////////////////////////// > >-IscSqlType::IscSqlType(int blrType, int subType, int length, int bufferLen, int dialect, int precision) >+IscSqlType::IscSqlType(int blrType, int subType, int length, int bufferLen, int dialect, int precision, int scale) > { >- getType (blrType, subType, length, bufferLen, dialect, precision); >+ getType (blrType, subType, length, bufferLen, dialect, precision, scale); > } > > IscSqlType::~IscSqlType() >@@ -52,11 +53,11 @@ > > } > >-void IscSqlType::getType(int blrType, int subType, int len, int bufferLen, int dialect, int precision) >+void IscSqlType::getType(int blrType, int subType, int len, int bufferLen, int dialect, int precision, int scale) > { > length = len; > bufferLength = bufferLen; >- >+ > switch (blrType) > { > case blr_text: >@@ -176,21 +177,25 @@ > } > } > >- if (type == JDBC_SMALLINT || type == JDBC_INTEGER || type == JDBC_BIGINT) >- { >- if (subType == 1) >- { >- type = JDBC_NUMERIC; >- typeName = "NUMERIC"; >- length = precision; >- bufferLength = MAX_DECIMAL_LENGTH + 2; >- } >- else if (subType == 2) >- { >- type = JDBC_DECIMAL; >- typeName = "DECIMAL"; >- length = precision; >- bufferLength = MAX_DECIMAL_LENGTH + 2; >- } >+ if (type == JDBC_SMALLINT || type == JDBC_INTEGER || >+ type == JDBC_BIGINT || type == JDBC_DOUBLE) >+ { >+ if(scale < 0) >+ { >+ if (subType == 2) >+ { >+ type = JDBC_DECIMAL; >+ typeName = "DECIMAL"; >+ length = precision; >+ bufferLength = MAX_DECIMAL_LENGTH + 2; >+ } >+ else >+ { >+ type = JDBC_NUMERIC; >+ typeName = "NUMERIC"; >+ length = precision; >+ bufferLength = MAX_DECIMAL_LENGTH + 2; >+ } >+ } > } > } > > -- Thomas Miller Delphi Client/Server Certified Developer BSS Accounting & Distribution Software BSS Enterprise Accounting FrameWork http://www.bss-software.com |
From:
<car...@te...> - 2002-11-22 22:19:15
|
Hello: This patch allow to numeric and decimal datatypes to be reported well on some catalog functions instead of as they are stored on firebird databases. Best regards Carlos Guzmán Álvarez Vigo-Spain |
From: Thomas M. <tm...@bs...> - 2002-11-22 21:23:03
|
I have narrowed down the number problem. Basically any number between .10 and .99 displays as a hole number. .37 displays as 370,000. .09 displays as .09 1.23 displays as 1.23 The field type is NUMERIC(18,6) Paul Reeves wrote: > > A new snapshot of the driver is available here: > > http://www.ibphoenix.com/downloads/OdbcJdbc-20021122-snapshot.zip > > All in all it seems to behave a lot better now with applications such > as MS Access. We probably still have a little way to go, but this > snapshot is well worth testing. > > Many thanks are due to Carlos Alvarez who has contributed many fixes. > Much of the work has been in the area of 'compliance'. Applications > such as Access do a lot of metadata querying and ask lots of questions > about driver capabilities. Get the answer wrong and the application > often gives up, or gets very confused. > > None of this has very much to do with actual data access. The core > part of the driver - sending SQL to the server has remained largely > untouched - because it works. > > Feedback to this list is very welcome. > > > Paul -- Thomas Miller Delphi Client/Server Certified Developer BSS Accounting & Distribution Software BSS Enterprise Accounting FrameWork http://www.bss-software.com |
From: Wieslaw P. <wie...@po...> - 2002-11-22 20:03:59
|
> > Feedback to this list is very welcome. I tried to use the driver with Oracle SQL*Plus and Oracle Forms and received log I placed below. The query was select 1 from ml_sta_vat mL_sta_vat has several rows, but the query returns only one; Wiesiek masterkey@odbc: 214-5b8 ENTER SQLPrepare HSTMT 01451F10 UCHAR * 0x0129F78C [ 25] "select 1 from ml_sta_vat " SDWORD 25 masterkey@odbc: 214-5b8 EXIT SQLPrepare with return code 0 (SQL_SUCCESS) HSTMT 01451F10 UCHAR * 0x0129F78C [ 25] "select 1 from ml_sta_vat " SDWORD 25 masterkey@odbc: 214-5b8 ENTER SQLExecute HSTMT 01451F10 masterkey@odbc: 214-5b8 EXIT SQLExecute with return code 0 (SQL_SUCCESS) HSTMT 01451F10 masterkey@odbc: 214-5b8 ENTER SQLNumResultCols HSTMT 01451F10 SWORD * 0x0012D5D4 masterkey@odbc: 214-5b8 EXIT SQLNumResultCols with return code 0 (SQL_SUCCESS) HSTMT 01451F10 SWORD * 0x0012D5D4 (1) masterkey@odbc: 214-5b8 ENTER SQLDescribeCol HSTMT 01451F10 UWORD 1 UCHAR * 0x0012D590 SWORD 32 SWORD * 0x0012D4DC SWORD * 0x0012D4A8 SQLULEN * 0x0012D4A4 SWORD * 0x0012D4E4 SWORD * 0x0012D49C masterkey@odbc: 214-5b8 EXIT SQLDescribeCol with return code 0 (SQL_SUCCESS) HSTMT 01451F10 UWORD 1 UCHAR * 0x0012D590 SWORD 32 SWORD * 0x0012D4DC (0) SWORD * 0x0012D4A8 (4) SQLULEN * 0x0012D4A4 (10) SWORD * 0x0012D4E4 (0) SWORD * 0x0012D49C (0) masterkey@odbc: 214-5b8 ENTER SQLColAttributes HSTMT 01451F10 UWORD 1 UWORD 3 <SQL_COLUMN_LENGTH> PTR 0x00000000 SWORD 0 SWORD * 0x00000000 SQLLEN * 0x0012D4B0 masterkey@odbc: 214-5b8 EXIT SQLColAttributes with return code 0 (SQL_SUCCESS) HSTMT 01451F10 UWORD 1 UWORD 3 <SQL_COLUMN_LENGTH> PTR 0x00000000 SWORD 0 SWORD * 0x00000000 SQLLEN * 0x0012D4B0 (11) masterkey@odbc: 214-5b8 ENTER SQLSetStmtOption HSTMT 01451F10 UWORD 9 <SQL_ROWSET_SIZE> SQLPOINTER 0x0000000F masterkey@odbc: 214-5b8 EXIT SQLSetStmtOption with return code 0 (SQL_SUCCESS) HSTMT 01451F10 UWORD 9 <SQL_ROWSET_SIZE> SQLPOINTER 0x0000000F (BADMEM) masterkey@odbc: 214-5b8 ENTER SQLBindCol HSTMT 01451F10 UWORD 1 SWORD 1 <SQL_C_CHAR> PTR 0x012A474C SQLLEN 50 SQLLEN * 0x0129F68C masterkey@odbc: 214-5b8 EXIT SQLBindCol with return code 0 (SQL_SUCCESS) HSTMT 01451F10 UWORD 1 SWORD 1 <SQL_C_CHAR> PTR 0x012A474C SQLLEN 50 SQLLEN * 0x0129F68C (19525688) masterkey@odbc: 214-5b8 ENTER SQLExtendedFetch HSTMT 01451F10 UWORD 1 <SQL_FETCH_NEXT> SQLLEN 15 SQLULEN * 0x0012D6AC UWORD * 0x0129F56C masterkey@odbc: 214-5b8 EXIT SQLExtendedFetch with return code 0 (SQL_SUCCESS) HSTMT 01451F10 UWORD 1 <SQL_FETCH_NEXT> SQLLEN 15 SQLULEN * 0x0012D6AC (1) UWORD * 0x0129F56C (0) masterkey@odbc: 214-5b8 ENTER SQLFreeStmt HSTMT 01451F10 UWORD 1 <SQL_DROP> masterkey@odbc: 214-5b8 EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS) HSTMT 01451F10 UWORD 1 <SQL_DROP> |
From: <psc...@in...> - 2002-11-22 15:18:21
|
Dear List: A couple of questions 1) Has anyone tried this driver with the wxODBC class that is part of wxWindows? If not, I shall be testing it in about 2-3 weeks, to see what happens, I will let this list know the results. 2) Since the driver is a DLL, is there any way to get VC++ to kick the DLL into debug mode, to see why things that should be working do not. I would guess you need to get the DLL to "crash" at some point, but is there a clean way to do this? |
From: Paul R. <pr...@ib...> - 2002-11-22 15:09:08
|
A new snapshot of the driver is available here: http://www.ibphoenix.com/downloads/OdbcJdbc-20021122-snapshot.zip All in all it seems to behave a lot better now with applications such as MS Access. We probably still have a little way to go, but this snapshot is well worth testing. Many thanks are due to Carlos Alvarez who has contributed many fixes. Much of the work has been in the area of 'compliance'. Applications such as Access do a lot of metadata querying and ask lots of questions about driver capabilities. Get the answer wrong and the application often gives up, or gets very confused. None of this has very much to do with actual data access. The core part of the driver - sending SQL to the server has remained largely untouched - because it works. Feedback to this list is very welcome. Paul -- Paul Reeves http://www.ibphoenix.com Supporting users of Firebird and InterBase |
From: Paul S. <wo...@ca...> - 2002-11-22 13:41:59
|
Testing, please ignore.... |
From: Thomas M. <tm...@bs...> - 2002-11-21 20:49:50
|
I use a lot of NUMERIC(15,0) NUMERIC(15,6) NUMERIC(7,4) NUMERIC(4,0) Carlos Guzmán Álvarez wrote: > Hello: > > > >> Could this be related to the datatype mangiling that Paul mentioned > >> for my number problem? > > I´m not sure, but i think that it can be. > > You have problems with numeric fields, no?? what is the exact datatype > of the field?? numeric, decimal or double?? and what it´s it length > and precision?? i can try to make some tests if i have time > > > > Best regards > Carlos Guzmán Álvarez > Vigo-Spain > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Firebird-odbc-devel mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel > -- Thomas Miller Delphi Client/Server Certified Developer BSS Accounting & Distribution Software BSS Enterprise Accounting FrameWork http://www.bss-software.com |
From: Paul R. <pr...@ib...> - 2002-11-21 19:39:02
|
Carlos Guzm=E1n =C1lvarez wrote: > Hello: >=20 >=20 > I send a patch for the dates on acces, but this continues to have probl= ems: >=20 >=20 Thanks for these - I shall a look at them tomorrow. > - Dates - Works well ( as i see on my tests ). >=20 > - Time - Gives conversion error ( as i see on my tests ). >=20 > - TimeStamp - Gives conversion error ( as i see on my tests ). >=20 Yes - timestamp was the datatype that was causing me problems. By the=20 time it reached Access it had been turned into a blob. Forcing it to be=20 a different datatype (in ODBCStatement) didn't get me much further. Paul --=20 Paul Reeves http://www.ibphoenix.com Supporting users of Firebird and InterBase |
From: <car...@te...> - 2002-11-21 19:18:54
|
Hello: >> Could this be related to the datatype mangiling that Paul mentioned >> for my number problem? I´m not sure, but i think that it can be. You have problems with numeric fields, no?? what is the exact datatype of the field?? numeric, decimal or double?? and what it´s it length and precision?? i can try to make some tests if i have time Best regards Carlos Guzmán Álvarez Vigo-Spain |
From: Thomas M. <tm...@bs...> - 2002-11-21 19:10:21
|
Could this be related to the datatype mangiling that Paul mentioned for my number problem? Carlos Guzmán Álvarez wrote: > Hello: > > > I send a patch for the dates on acces, but this continues to have > problems: > > > - Dates - Works well ( as i see on my tests ). > > - Time - Gives conversion error ( as i see on my tests ). > > - TimeStamp - Gives conversion error ( as i see on my tests ). > > > > > > Best regards > Carlos Guzmán Álvarez > Vigo-Spain > >------------------------------------------------------------------------ > >Index: IscSqlType.cpp >=================================================================== >RCS file: /cvsroot/firebird/OdbcJdbc/IscDbc/IscSqlType.cpp,v >retrieving revision 1.2 >diff -u -r1.2 IscSqlType.cpp >--- IscSqlType.cpp 11 Oct 2002 11:09:06 -0000 1.2 >+++ IscSqlType.cpp 21 Nov 2002 18:57:18 -0000 >@@ -109,15 +109,6 @@ > } > break; > >- case blr_timestamp: >- { >- type = JDBC_TIMESTAMP; >- typeName = "TIMESTAMP"; >- length = MAX_TIMESTAMP_LENGTH; >- bufferLength = length; >- } >- break; >- > case blr_varying: > case blr_varying2: > { >@@ -145,7 +136,7 @@ > > case blr_sql_date: > { >- type = JDBC_DATE; >+ type = JDBC_SQL_DATE; > typeName = "DATE"; > length = MAX_DATE_LENGTH; > bufferLength = length; >@@ -154,10 +145,19 @@ > > case blr_sql_time: > { >- type = JDBC_TIME; >+ type = JDBC_SQL_TIME; > typeName = "TIME"; > length = MAX_TIME_LENGTH; > bufferLength = length-2; >+ } >+ break; >+ >+ case blr_timestamp: >+ { >+ type = JDBC_SQL_TIMESTAMP; >+ typeName = "TIMESTAMP"; >+ length = MAX_TIMESTAMP_LENGTH; >+ bufferLength = length; > } > break; > > > >------------------------------------------------------------------------ > >Index: IscDbc.h >=================================================================== >RCS file: /cvsroot/firebird/OdbcJdbc/IscDbc/IscDbc.h,v >retrieving revision 1.4 >diff -u -r1.4 IscDbc.h >--- IscDbc.h 11 Oct 2002 11:09:05 -0000 1.4 >+++ IscDbc.h 21 Nov 2002 18:57:01 -0000 >@@ -82,6 +82,10 @@ > #define JDBC_VARCHAR 12 > #define JDBC_LONGVARCHAR -1 > >+#define JDBC_SQL_DATE 9 >+#define JDBC_SQL_TIME 10 >+#define JDBC_SQL_TIMESTAMP 11 >+ > #define JDBC_DATE 91 > #define JDBC_TIME 92 > #define JDBC_TIMESTAMP 93 > > -- Thomas Miller Delphi Client/Server Certified Developer BSS Accounting & Distribution Software BSS Enterprise Accounting FrameWork http://www.bss-software.com |