libopendbx-devel Mailing List for OpenDBX database access library (Page 3)
Brought to you by:
nose
You can subscribe to this list here.
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2008 |
Jan
(20) |
Feb
(18) |
Mar
(2) |
Apr
(13) |
May
(6) |
Jun
(65) |
Jul
(32) |
Aug
(58) |
Sep
(60) |
Oct
(15) |
Nov
(7) |
Dec
(35) |
2009 |
Jan
(29) |
Feb
(2) |
Mar
(35) |
Apr
(20) |
May
(76) |
Jun
(50) |
Jul
(13) |
Aug
(35) |
Sep
(71) |
Oct
(20) |
Nov
(3) |
Dec
(37) |
2010 |
Jan
(11) |
Feb
(10) |
Mar
(33) |
Apr
(17) |
May
(4) |
Jun
(9) |
Jul
(19) |
Aug
(13) |
Sep
(9) |
Oct
|
Nov
|
Dec
(2) |
2011 |
Jan
(13) |
Feb
|
Mar
(12) |
Apr
(1) |
May
(22) |
Jun
(12) |
Jul
(34) |
Aug
(12) |
Sep
(7) |
Oct
(6) |
Nov
|
Dec
(1) |
2012 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(23) |
Jun
(7) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2013 |
Jan
|
Feb
(4) |
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(18) |
Nov
|
Dec
|
2014 |
Jan
(6) |
Feb
|
Mar
|
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(8) |
Nov
|
Dec
|
From: Norbert S. <no...@li...> - 2012-06-10 21:54:48
|
Hi Guille > I was wandering when will you release a new version of OpenDBX with the > latest fixes :). Maybe you still have stuff to add... > I can try to build the windows binares for most platforms -if not all- to > put in the website but not before I know you freeze it ;). I've integrated the last fix and the last revision in SVN will be the base of the new 1.4.6 version. Norbert |
From: Norbert S. <no...@li...> - 2012-05-24 22:42:56
|
Hi Murray > See http://archives.postgresql.org/pgsql-bugs/2011-01/msg00097.php for my bug report and the ensuing conversation. After reading though the discussion, another option might more elegant: If PQresultStatus() returns PGRES_FATAL_ERROR, we can call PQconsumeInput() to be sure, the call to PQStatus() knowns what's going on: case PGRES_FATAL_ERROR: + PQconsumeInput( (PGconn*) handle->generic ); if( PQstatus( (PGconn*) handle->generic ) != CONNECTION_OK ) Could you test if this has the desired effect? Norbert |
From: Murray S. K. <ms...@cl...> - 2012-05-24 17:54:23
|
> -----Original Message----- > From: Norbert Sendetzky [mailto:no...@li...] > Sent: Wednesday, May 23, 2012 1:55 AM > To: OpenDBX devel list > Subject: Re: [opendbx] new OpenDBX 1.4 stable release? > > Hi Guille > > > I was wandering when will you release a new version of OpenDBX with > > the latest fixes :). Maybe you still have stuff to add... > > I can try to build the windows binares for most platforms -if not all- > > to put in the website but not before I know you freeze it ;). > > Yes, there's one open task left: A workaround for the broken PostgreSQL > error handling reported by Murray. My workaround isn't pretty: If odbx_query() fails and the error string returned by PostgreSQL via odbx_error() starts with "FATAL:", then ignore the error type reported by odbx_error_type() and force a manual reconnect attempt. If that still fails, then abort completely. The issue is that PQstatus() can return CONNECTION_OK when it's not. In particular, even after a result request returns a fatal error, PQstatus() reports the connection is okay, which in turn confuses OpenDBX. This is easily reproduced by making a connection via OpenDBX, issuing a query and getting its results, then restarting PostgreSQL, then repeating the query. Although the connection is most assuredly dead now, PQstatus() says it's fine. See http://archives.postgresql.org/pgsql-bugs/2011-01/msg00097.php for my bug report and the ensuing conversation. -MSK |
From: Norbert S. <no...@li...> - 2012-05-23 08:54:50
|
Hi Guille > I was wandering when will you release a new version of OpenDBX with the > latest fixes :). Maybe you still have stuff to add... > I can try to build the windows binares for most platforms -if not all- to > put in the website but not before I know you freeze it ;). Yes, there's one open task left: A workaround for the broken PostgreSQL error handling reported by Murray. Norbert |
From: Guillermo P. <gui...@gm...> - 2012-05-23 08:38:14
|
Hi Norbert! I was wandering when will you release a new version of OpenDBX with the latest fixes :). Maybe you still have stuff to add... I can try to build the windows binares for most platforms -if not all- to put in the website but not before I know you freeze it ;). Cheers, Guille |
From: Facundo V. <fac...@gm...> - 2012-05-09 15:51:47
|
I haven't time to try it yet. Could compile the tools on Windows? If not I could try it later today. Thanks On Wed, May 9, 2012 at 12:07 PM, Guillermo Polito <gui...@gm... > wrote: > Perfect, I checkouted and everything compiled from scratch with no need > to touch anything in windows :). > > > On Wed, May 9, 2012 at 4:42 PM, Guillermo Polito < > gui...@gm...> wrote: > >> Nice, merge is coming :) >> >> Thanks >> >> >> On Wed, May 9, 2012 at 4:41 PM, Norbert Sendetzky < >> no...@li...> wrote: >> >>> Hi Guille >>> >>> > What is the url of the svn repo you are using? :) I'm looking at: >>> > https://libopendbx.svn.sourceforge.net/svnroot/libopendbx/trunk/ >>> >>> I'm currently committing to >>> >>> >>> https://libopendbx.svn.sourceforge.net/svnroot/libopendbx/branches/stable-1.4/ >>> >>> because I would like to make a new stable release. Afterwards, I will >>> also merge the changes to the trunk :-) >>> >>> >>> Norbert >>> >>> >>> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. Discussions >>> will include endpoint security, mobile security and the latest in malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> libopendbx-devel mailing list >>> lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel >>> http://www.linuxnetworks.de/doc/index.php/OpenDBX >>> >> >> > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > libopendbx-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/libopendbx-devel > http://www.linuxnetworks.de/doc/index.php/OpenDBX > > |
From: Guillermo P. <gui...@gm...> - 2012-05-09 15:09:41
|
On Sun, May 6, 2012 at 5:02 PM, Norbert Sendetzky <no...@li...>wrote: > Hi Guille > > > 1> select * from ((select t1.c1, null t3 from test t1 where t1.c1 is not > > null) U > > NION ALL (select NULL t3, t2.c2 from test t2 where t2.c2 is not null)) tt > > 2> go > > c1 t3 > > 1 NULL > > NULL 3 > > (2 rows affected) > > I think I've found the problem in the MSSQL code (the NULL indicator > wasn't set correctly). Could you update to SVN rev. 363 or later and > check if your problem is solved now? > Yes, I found the same and was about to report before noticing the svn revisions were different. FYI -> This is fixed with the patch :) Thanks! > > Thanks > > > Norbert > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > libopendbx-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/libopendbx-devel > http://www.linuxnetworks.de/doc/index.php/OpenDBX > |
From: Guillermo P. <gui...@gm...> - 2012-05-09 15:07:35
|
Perfect, I checkouted and everything compiled from scratch with no need to touch anything in windows :). On Wed, May 9, 2012 at 4:42 PM, Guillermo Polito <gui...@gm...>wrote: > Nice, merge is coming :) > > Thanks > > > On Wed, May 9, 2012 at 4:41 PM, Norbert Sendetzky < > no...@li...> wrote: > >> Hi Guille >> >> > What is the url of the svn repo you are using? :) I'm looking at: >> > https://libopendbx.svn.sourceforge.net/svnroot/libopendbx/trunk/ >> >> I'm currently committing to >> >> >> https://libopendbx.svn.sourceforge.net/svnroot/libopendbx/branches/stable-1.4/ >> >> because I would like to make a new stable release. Afterwards, I will >> also merge the changes to the trunk :-) >> >> >> Norbert >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> libopendbx-devel mailing list >> lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel >> http://www.linuxnetworks.de/doc/index.php/OpenDBX >> > > |
From: Guillermo P. <gui...@gm...> - 2012-05-09 14:42:27
|
Nice, merge is coming :) Thanks On Wed, May 9, 2012 at 4:41 PM, Norbert Sendetzky <no...@li...>wrote: > Hi Guille > > > What is the url of the svn repo you are using? :) I'm looking at: > > https://libopendbx.svn.sourceforge.net/svnroot/libopendbx/trunk/ > > I'm currently committing to > > > https://libopendbx.svn.sourceforge.net/svnroot/libopendbx/branches/stable-1.4/ > > because I would like to make a new stable release. Afterwards, I will > also merge the changes to the trunk :-) > > > Norbert > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > libopendbx-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/libopendbx-devel > http://www.linuxnetworks.de/doc/index.php/OpenDBX > |
From: Norbert S. <no...@li...> - 2012-05-09 14:41:23
|
Hi Guille > What is the url of the svn repo you are using? :) I'm looking at: > https://libopendbx.svn.sourceforge.net/svnroot/libopendbx/trunk/ I'm currently committing to https://libopendbx.svn.sourceforge.net/svnroot/libopendbx/branches/stable-1.4/ because I would like to make a new stable release. Afterwards, I will also merge the changes to the trunk :-) Norbert |
From: Guillermo P. <gui...@gm...> - 2012-05-09 14:37:42
|
On Wed, May 9, 2012 at 4:32 PM, Norbert Sendetzky <no...@li...>wrote: > Hi Guille > > > I was trying to compile mssql backend on windows (yes, I know odbc is > > recomended :P) and I was having problems with the libintl again with > Mingw. > > > > I kind of solve this changing the makefile in mssql backend folder. I've > > changed > > > > LDFLAGS = -L/usr/local/lib -L/c/mingw/lib > > > > by > > > > LDFLAGS = -L/usr/local/lib -L/c/mingw/lib ${LTLIBINTL} > > > > And I could compile. I'm not too versed in makefiles, so you probably > will > > find a more elegant solution for this. Meanwhile, I'm happy I have my > dll > > :). > > I've added the same check as for the sqlite3 backend in order to add the > libintl library if necessary. Available since SVN rev. 365. > > Could you give it a try if it build also this way on your machine? > What is the url of the svn repo you are using? :) I'm looking at: https://libopendbx.svn.sourceforge.net/svnroot/libopendbx/trunk/ which is the one that says in http://www.linuxnetworks.de/doc/index.php/OpenDBX And can see only up to revision 355. Probably that's why Mariano and I couldn't see the fixes :). Cheers, Guille > > Thanks > > > Norbert > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > libopendbx-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/libopendbx-devel > http://www.linuxnetworks.de/doc/index.php/OpenDBX > |
From: Norbert S. <no...@li...> - 2012-05-09 14:33:04
|
Hi Guille > I was trying to compile mssql backend on windows (yes, I know odbc is > recomended :P) and I was having problems with the libintl again with Mingw. > > I kind of solve this changing the makefile in mssql backend folder. I've > changed > > LDFLAGS = -L/usr/local/lib -L/c/mingw/lib > > by > > LDFLAGS = -L/usr/local/lib -L/c/mingw/lib ${LTLIBINTL} > > And I could compile. I'm not too versed in makefiles, so you probably will > find a more elegant solution for this. Meanwhile, I'm happy I have my dll > :). I've added the same check as for the sqlite3 backend in order to add the libintl library if necessary. Available since SVN rev. 365. Could you give it a try if it build also this way on your machine? Thanks Norbert |
From: Norbert S. <no...@li...> - 2012-05-09 14:22:21
|
Hi Guille >> From the odbc docs I assume the right lengths for datetimes are more like > > case SQL_DATE: > case SQL_TYPE_DATE: > return 11; > case SQL_TIME: > case SQL_TYPE_TIME: > return 9; > case SQL_TIMESTAMP: > case SQL_TYPE_TIMESTAMP: > return 24; > > I've checked the latest sources with and without the fix and it works fine > with my changes. > > Can we add them? :) No problem, changed in SVN rev 364. Norbert |
From: Guillermo P. <gui...@gm...> - 2012-05-09 13:45:40
|
Ok, finally I'm getting into the Windoze world and trying to solve this :). The truncation seems to be a buffer problem. Whay I'm looking is that the types length described in http://msdn.microsoft.com/en-us/library/bb677267.aspx does not fit with the length in odbc_priv_collength. >From the odbc docs I assume the right lengths for datetimes are more like case SQL_DATE: case SQL_TYPE_DATE: return 11; case SQL_TIME: case SQL_TYPE_TIME: return 9; case SQL_TIMESTAMP: case SQL_TYPE_TIMESTAMP: return 24; I've checked the latest sources with and without the fix and it works fine with my changes. Can we add them? :) Guille On Fri, Jul 15, 2011 at 2:41 PM, Guillermo Polito <gui...@gm... > wrote: > What puzzles me is that the insert is successful and I can execute querys > from the SQL management studio and they work. > > I'll try inserting a value like that. > > Thanks! > > > On Fri, Jul 15, 2011 at 9:35 AM, Norbert Sendetzky < > no...@li...> wrote: > >> Hi Guille >> >> > Create table test4 (fechia datetime) >> > insert into test4 values(''10-10-10'') >> > >> > select * from test4 -> [Microsoft][ODBC SQL Server Driver]String data, >> > right truncation >> > >> > ¿Is it a known issue? >> >> No, no that I'm aware of, but your value is wrong. Can you try >> '2010-10-10 00:00:00'? >> > > >> Norbert >> >> >> ------------------------------------------------------------------------------ >> AppSumo Presents a FREE Video for the SourceForge Community by Eric >> Ries, the creator of the Lean Startup Methodology on "Lean Startup >> Secrets Revealed." This video shows you how to validate your ideas, >> optimize your ideas and identify your business strategy. >> http://p.sf.net/sfu/appsumosfdev2dev >> _______________________________________________ >> libopendbx-devel mailing list >> lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel >> http://www.linuxnetworks.de/doc/index.php/OpenDBX >> > > |
From: Norbert S. <no...@li...> - 2012-05-09 11:07:24
|
Hi Mariano > INSERT INTO student (id, name_surname, nullable_field) VALUES (88, > ''Mariano Squeak'', null) . > INSERT INTO student (id, name_surname, nullable_field) VALUES (89, > ''Mariano Squeak'', ''riptobe'' ) > > SELECT id, nullable_field FROM student > > And then I get all the rows of the resultset. But still, for "riptobe" we > have an 16rFF 255 type :( The record including 'riptobe' shouldn't have been of type unknown (255) before. Only the first one (id 88) was of type 255 before applying the patch. > I even recompiled/installed Sqlite3 with the option > SQLITE_ENABLE_COLUMN_METADATA as suggested here: > http://source.online.free.fr/Linux_HowToCompileSQLite.html Can you have a look if the function are really available in your sqlite3 library? nm -D /usr/lib/libsqlite3.so (or wherever it's located) You should then see something like: 000095a0 T sqlite3_column_database_name 000096a0 T sqlite3_column_origin_name 00009620 T sqlite3_column_table_name 0005a1a0 T sqlite3_table_column_metadata When running the test suite (./test/odbxtest ...), it works pretty well on my machine. Norbert |
From: Mariano M. P. <mar...@gm...> - 2012-05-09 10:52:22
|
On Sun, May 6, 2012 at 2:21 PM, Norbert Sendetzky <no...@li...>wrote: > Hi all > > > Yes, that is what is expected, but in the case of SQLite, the column > > type changes to SQLITE_NULL for nulls and that is a problem in > > squeakdbx now. I think column datatype should not be stored in the > > resultset in the case of sqlite. Other databases don't behave this > > way (as far as I can remember), so, overriding moveNext for sqlite > > would probably be fine. > > I've enhanced the way to find out what is the data type of the column > even if SQLite3 returns SQLITE_NULL as column type when one row contains > a value of NULL. > > SQLite3 provides a function sqlite3_table_column_metadata() which > returns the original column information when SQLite3 is compiled with > the marco SQLITE_ENABLE_COLUMN_METADATA (which should usually be the case). > > The enhancement is available since SVN rev. 362 > > Norbert, I tried but still couldn't make it work. What I am doing as a test is this: CREATE TABLE student( id INTEGER, name_surname CHARACTER VARYING(30), username VARCHAR(10), pass VARCHAR(10), mail VARCHAR(50), regular BOOLEAN, age SMALLINT, average_grade DECIMAL(9,3), sex CHARACTER(3), description CHARACTER VARYING(200), starting_hour TIME, sign_up_date TIMESTAMP, born_date DATE, nullable_field VARCHAR(64) NULL, CONSTRAINT pk_students_id PRIMARY KEY (id) ) INSERT INTO student (id, name_surname, nullable_field) VALUES (88, ''Mariano Squeak'', null) . INSERT INTO student (id, name_surname, nullable_field) VALUES (89, ''Mariano Squeak'', ''riptobe'' ) SELECT id, nullable_field FROM student And then I get all the rows of the resultset. But still, for "riptobe" we have an 16rFF 255 type :( I even recompiled/installed Sqlite3 with the option SQLITE_ENABLE_COLUMN_METADATA as suggested here: http://source.online.free.fr/Linux_HowToCompileSQLite.html Any idea? thanks > > Norbert > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > libopendbx-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/libopendbx-devel > http://www.linuxnetworks.de/doc/index.php/OpenDBX > -- Mariano http://marianopeck.wordpress.com |
From: Guillermo P. <gui...@gm...> - 2012-05-08 22:55:59
|
Hi Norbert! I was trying to compile mssql backend on windows (yes, I know odbc is recomended :P) and I was having problems with the libintl again with Mingw. I kind of solve this changing the makefile in mssql backend folder. I've changed LDFLAGS = -L/usr/local/lib -L/c/mingw/lib by LDFLAGS = -L/usr/local/lib -L/c/mingw/lib ${LTLIBINTL} And I could compile. I'm not too versed in makefiles, so you probably will find a more elegant solution for this. Meanwhile, I'm happy I have my dll :). Thanks! Guille PS: tomorrow we will be testing all the other stuff you fixed and integrated :3 Thanks thanks thanks On Sun, May 6, 2012 at 12:04 PM, Norbert Sendetzky <no...@li... > wrote: > Hi all > > >> Just to let you know that I finally solved this problem adding > >> LDFLAGS = -lintl > >> to the sqlite3 backend makefile of opendbx > >> I think a better way to do this would be to add it somwhere in the > >> configure script. > > > > Norbert, do you think this should be added to OpenDBX makefiles? > > I've added some code in the configure script to test for libintl and add > it to the linker options if necessary. It's available since SVN rev. 358 > but I need somebody for testing this who had the problem before when > building OpenDBX with MinGW. > > > Norbert > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > libopendbx-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/libopendbx-devel > http://www.linuxnetworks.de/doc/index.php/OpenDBX > |
From: Norbert S. <no...@li...> - 2012-05-06 15:02:56
|
Hi Guille > 1> select * from ((select t1.c1, null t3 from test t1 where t1.c1 is not > null) U > NION ALL (select NULL t3, t2.c2 from test t2 where t2.c2 is not null)) tt > 2> go > c1 t3 > 1 NULL > NULL 3 > (2 rows affected) I think I've found the problem in the MSSQL code (the NULL indicator wasn't set correctly). Could you update to SVN rev. 363 or later and check if your problem is solved now? Thanks Norbert |
From: Norbert S. <no...@li...> - 2012-05-06 12:21:39
|
Hi all > Yes, that is what is expected, but in the case of SQLite, the column > type changes to SQLITE_NULL for nulls and that is a problem in > squeakdbx now. I think column datatype should not be stored in the > resultset in the case of sqlite. Other databases don't behave this > way (as far as I can remember), so, overriding moveNext for sqlite > would probably be fine. I've enhanced the way to find out what is the data type of the column even if SQLite3 returns SQLITE_NULL as column type when one row contains a value of NULL. SQLite3 provides a function sqlite3_table_column_metadata() which returns the original column information when SQLite3 is compiled with the marco SQLITE_ENABLE_COLUMN_METADATA (which should usually be the case). The enhancement is available since SVN rev. 362 Norbert |
From: Mariano M. P. <mar...@gm...> - 2012-05-06 12:12:14
|
On Sun, May 6, 2012 at 1:04 PM, Norbert Sendetzky <no...@li...>wrote: > Hi Guille > > > :3 Thanks!!! I'll test it asap :). > > Is it available on the binary distribution also? (if not I can build my > > own, just want to see how to distribute it for dbxtalk :) ). > > Currently, the fix is only in SVN. I'm trying to fix a few other issues > and will prepare a new release later on. > > Excellent! Thanks Norbert. > > Norbert > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > libopendbx-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/libopendbx-devel > http://www.linuxnetworks.de/doc/index.php/OpenDBX > -- Mariano http://marianopeck.wordpress.com |
From: Norbert S. <no...@li...> - 2012-05-06 11:04:35
|
Hi Guille > :3 Thanks!!! I'll test it asap :). > Is it available on the binary distribution also? (if not I can build my > own, just want to see how to distribute it for dbxtalk :) ). Currently, the fix is only in SVN. I'm trying to fix a few other issues and will prepare a new release later on. Norbert |
From: Guillermo P. <gui...@gm...> - 2012-05-06 11:01:09
|
:3 Thanks!!! I'll test it asap :). Is it available on the binary distribution also? (if not I can build my own, just want to see how to distribute it for dbxtalk :) ). Thank you very much!! Guille On Sun, May 6, 2012 at 12:39 PM, Norbert Sendetzky <no...@li... > wrote: > Hi all > > > static int sqlite3_odbx_row_fetch( odbx_result_t* result ) > > { > > case SQLITE_MISUSE: // Return DONE if function called more > often > > afterwards > > >> sqlite3_finalize( (sqlite3_stmt*) result->generic ); > > >> result->generic = NULL; > > return ODBX_ROW_DONE; > > } > > There was a change in the SQLite library starting after version 3.6.23.1 > (http://sqlite.org/c3ref/step.html) describing this issue. I've added > the two suggested lines in sqlite3_odbx_row_fetch() (available since SVN > rev. 360). > > > Norbert > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > libopendbx-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/libopendbx-devel > http://www.linuxnetworks.de/doc/index.php/OpenDBX > |
From: Norbert S. <no...@li...> - 2012-05-06 10:39:28
|
Hi all > static int sqlite3_odbx_row_fetch( odbx_result_t* result ) > { > case SQLITE_MISUSE: // Return DONE if function called more often > afterwards > >> sqlite3_finalize( (sqlite3_stmt*) result->generic ); > >> result->generic = NULL; > return ODBX_ROW_DONE; > } There was a change in the SQLite library starting after version 3.6.23.1 (http://sqlite.org/c3ref/step.html) describing this issue. I've added the two suggested lines in sqlite3_odbx_row_fetch() (available since SVN rev. 360). Norbert |
From: Norbert S. <no...@li...> - 2012-05-06 10:04:55
|
Hi all >> Just to let you know that I finally solved this problem adding >> LDFLAGS = -lintl >> to the sqlite3 backend makefile of opendbx >> I think a better way to do this would be to add it somwhere in the >> configure script. > > Norbert, do you think this should be added to OpenDBX makefiles? I've added some code in the configure script to test for libintl and add it to the linker options if necessary. It's available since SVN rev. 358 but I need somebody for testing this who had the problem before when building OpenDBX with MinGW. Norbert |
From: Norbert S. <no...@li...> - 2012-04-25 18:19:27
|
Hi Facundo > checking readline/readline.h usability... no > checking readline/readline.h presence... no > checking for readline/readline.h... no > configure: error: libreadline header (readline/readline.h) not found > > The GnuWin32 tools are installed on my computer. The utils are rather hard to build on Windows platforms. You need additional header files. You can find the links here: http://linuxnetworks.de/doc/index.php/OpenDBX/Setup/Windows/Building_with_MinGW#Requirements I've never tried to build this on 64 bit Windows platforms, so good luck :-) Norbert |