Menu
▾
▴
firebird-odbc-devel
|
From: Alexander P. <ale...@re...> - 2008-11-20 10:00:43
|
Hi all, ODBC Driver v.2 RC1 (2.0.0.148) got out, all packages (with sources and changelog) are available here: http://firebirdsql.org/index.php?op=files&id=odbc <http://firebirdsql.org/index.php?op=files&id=odbc> Please test these thoroughly and report experiences, good or bad, to the firebird-odbc-devel list. Regards Alexander -- Alexander Potapchenko http://www.red-soft.biz Senior developer |
|
From: Minoru Y. <yo...@ti...> - 2008-11-21 01:23:04
|
Hi, BLOB text column is not transliteration with UTF8 connection. http://tracker.firebirdsql.org/browse/ODBC-44 I retry it with RC1(Build 148 ). My environment: - FB V2.0.4 - Client connection: UTF8 Case 1. Defaut charset: UTF8 - VARCHAR is fine - BLOB text is NOT fine. Case 2. Default charset: SJIS_0208(japanese charset) - VARCHAR is fine - BLOB text is fine. (Of cause, characters range is SJIS_0208 only) I think that result must be the same at UTF8 client connection. Why is a result different? -- Regards, Minoru Alexander Potapchenko <ale...@re...> Thu, 20 Nov 2008 13:00:35 +0300 wrote: >Hi all, > >ODBC Driver v.2 RC1 (2.0.0.148) got out, all packages (with sources and >changelog) are available here: >http://firebirdsql.org/index.php?op=files&id=odbc ><http://firebirdsql.org/index.php?op=files&id=odbc> >Please test these thoroughly and report experiences, good or bad, to the >firebird-odbc-devel list. > >Regards >Alexander >-- >Alexander Potapchenko >http://www.red-soft.biz >Senior developer |
|
From: Alexander P. <ale...@re...> - 2008-11-21 08:05:39
|
Minoru Yoshida wrote: > Hi, > > BLOB text column is not transliteration with UTF8 connection. > http://tracker.firebirdsql.org/browse/ODBC-44 > > I retry it with RC1(Build 148 ). > > My environment: > > - FB V2.0.4 > - Client connection: UTF8 > > Case 1. Defaut charset: UTF8 > > - VARCHAR is fine > - BLOB text is NOT fine. > > Case 2. Default charset: SJIS_0208(japanese charset) > > - VARCHAR is fine > - BLOB text is fine. > (Of cause, characters range is SJIS_0208 only) > > I think that result must be the same at UTF8 client connection. > > Why is a result different? > I remember this strange problem (Firebird+ODBC+*ADO*), but my hands have not reached its decision still. :-) I will revert to consideration of this problem in the near future. -- Alexander Potapchenko http://www.red-soft.biz Senior developer |
|
From: Minoru Y. <yo...@ti...> - 2008-11-21 22:18:07
|
Alexander Potapchenko <ale...@re...> Fri, 21 Nov 2008 11:05:35 +0300 wrote: >Minoru Yoshida wrote: >> Hi, >> >> BLOB text column is not transliteration with UTF8 connection. >> http://tracker.firebirdsql.org/browse/ODBC-44 >> >> I retry it with RC1(Build 148 ). >> >> My environment: >> >> - FB V2.0.4 >> - Client connection: UTF8 >> >> Case 1. Defaut charset: UTF8 >> >> - VARCHAR is fine >> - BLOB text is NOT fine. >> >> Case 2. Default charset: SJIS_0208(japanese charset) >> >> - VARCHAR is fine >> - BLOB text is fine. >> (Of cause, characters range is SJIS_0208 only) >> >> I think that result must be the same at UTF8 client connection. >> >> Why is a result different? >> >I remember this strange problem (Firebird+ODBC+*ADO*), but my hands have >not reached its decision still. :-) >I will revert to consideration of this problem in the near future. I wait for your good decision. Thanks. -- Regards, Minoru |
|
From: eg <eg...@gm...> - 2008-12-04 17:22:44
|
Alexander Potapchenko wrote: > Hi all, > > ODBC Driver v.2 RC1 (2.0.0.148) got out, all packages (with sources and > changelog) are available here: > http://firebirdsql.org/index.php?op=files&id=odbc > <http://firebirdsql.org/index.php?op=files&id=odbc> > Please test these thoroughly and report experiences, good or bad, to the > firebird-odbc-devel list. > > Regards > Alexander I would like to test this with our embedded application. There does not seem to be a .lib file provided with the dll package. Is it possible to get one? I tried to make one (for VS2008) from the DLL using the procedure found in: http://support.microsoft.com/?id=131313 ... but I get connection errors at run time. Those errors are not there if I link my app with an older library and just drop the new DLL in place (so I am pretty sure the procedure didn't work). I know I can build it from sources... but then I also need to find the correct versions of firebird header files (ibase.h, iberror.h, etc). What version of these header files were used and should be used to build the odbcfb.dll? |
|
From: Alexander P. <ale...@re...> - 2008-12-10 16:01:56
|
eg wrote: > I would like to test this with our embedded application. > There does not seem to be a .lib file provided with the dll package. Is > it possible to get one? > I agree that it can be necessary and I will include *.lib and *.pdb files into ODBC Firebird driver RC2. > I tried to make one (for VS2008) from the DLL using the procedure found > in: http://support.microsoft.com/?id=131313 ... but I get connection > errors at run time. Those errors are not there if I link my app with an > older library and just drop the new DLL in place (so I am pretty sure > the procedure didn't work). > > I know I can build it from sources... but then I also need to find the > correct versions of firebird header files (ibase.h, iberror.h, etc). > What version of these header files were used and should be used to build > the odbcfb.dll? > You can use any Firebird header files from official releases. Header files from Firebird 2.1 and VS 2005 are used for ODBC Firebird driver V2 build. Regards, Alexander -- Alexander Potapchenko http://www.red-soft.biz Senior developer |
|
From: eg <eg...@gm...> - 2008-12-11 20:43:57
|
Alexander Potapchenko wrote: > eg wrote: >> > I agree that it can be necessary and I will include *.lib and *.pdb > files into ODBC Firebird driver RC2. That would be much appreciated. >> > You can use any Firebird header files from official releases. Header > files from Firebird 2.1 and VS 2005 are used for ODBC Firebird driver V2 > build. > The structure of the header file relationships and the build set up seems to have changed between FB 2.0 and FB 2.1.1 I just downloaded Fb 2.1.1. sources, and the odbc sources. I then opened the OdbcFB.sln with VS 2005. I noticed an added include directory named c:\firebird\include in the solution. The build.bat file has commnents that you copy over the necessary firebird include files such as ibase.h and iberror.h to there and build. I ended up with ib_util.h, perf.h, types_pub.h and then noticed that ibase.h is now referring to "../jrd/dsc_pub.h" so of course this doesn't quite work. I am thinking that the solution file OdbcJdbc\Builds\MsVc80.win\OdbcFb.sln doesnt quite work out of the box. Is there a recommended setup for this to build odbcfb properly with vs2005 (or 2003 or 2008) and the firebird 2.1.1 source files? What I did was arrange my source tree as follows: Fb | -- Firebird-2.1.1.17910-0 | -- OdbcJdbc | -- include The include directory is where I placed the copies of the various firebird include files (and I tweaked the solution file to point to it) To finally get it to work, what I ended up doing instead was to change the solution so that it adds additional includes for the various include and source subdirectories under \Firebird-2.1.1.17910-0. The challenge is that the firebird include files seem to be in multiple different subdirectories under \Firebird-2.1.1.17910-0.. which I had to hunt down. Specifically, I added the following include subdirectories to the solution: src\include src\include\gen src\jrd That seems to build (albeit with 182 warnings.. most of which seem to be the annoying sprintf / strcpy variety). If there is another way, please let me know. If not, perhaps this message will help others build ODBC from the sources on windows from the solution file. |
|
From: eg <eg...@gm...> - 2008-12-12 17:46:23
|
On Thu, Dec 11, 2008 at 9:34 PM, Alexander Potapchenko <ale...@re...> wrote: > eg wrote: >> Specifically, I added the following include subdirectories to the >> solution: >> >> src\include >> src\include\gen >> src\jrd >> > You need use Firebird headers files after Sed processing. Generally Firebird > sources is not required for ODBC driver build. > Ready header files for using are located in the Firebird\include\ directory > of the installed (or built) server. > Doh... I didn't even think to look at the server install for the includes, I looked directly at the server sources. That certainly makes it easier. Thanks Alexander. Regards, Ed p.s.: I am replying back on - list... sorry for the direct cc |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X