libzdb-general February 2008

libzdb-general@tildeslash.com

2 participants
3 discussions

Connection_lastRowId on postgresql
by Paul J Stevens 03 May '08

03 May '08

Jan-Henrik, This call always returns 0 on a postgresql connection. I assume this is because my tables are without OIDs. Is that intentional? I can work around it. But perhaps a small note in the api docs would be in order? -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl

2 15

[Announce] libzdb 2.1
by Jan-Henrik Haukeland 04 Mar '08

04 Mar '08

Version 2.1 of Zild Database Library is available: Download: http://www.tildeslash.com/libzdb/dist/libzdb-2.1.tar.gz MD5 checksum: 5abec56051f105cacb6dcec237a1d989 Change log: http://www.tildeslash.com/libzdb/dist/CHANGES.txt This is a feature release which has been tested on the following platforms: Darwin 9.1.0 [ppc/x86] Linux Ubuntu [x86] Changes in this release: Version 2.1 ----------- * API: Connection_ping is promoted to a public method. Clients can use this method to test if a Connection is alive. * API: Connection_clear() is exposed as a public method. Normally it is not necessary to call this method, but in some situations, if you use PreparedStatement_executeQuery it is necessary to call this function to close a prepared statement explicit. Basically, if you see this SQLite error, "SQL statements in progress", call this function to close any previous opened statements before proceeding. * Upon returning a Connection, the Connection Pool previously tried to commit a Connection if it was in a non-committed state, while now it rollback instead, which is assumed to be more correct. * Improved retry when SQLite report database lock, which should reduce the chance to meet the infamous SQLite "database is locked" error * Removed section 3 from "Tildeslash License Exception" so libzdb is licensed clear and permissive. * Internal optimizing changes

3 12

postgres wont do preparedstatements
by Paul J Stevens 25 Feb '08

25 Feb '08

Jan-Henrik, So I converted dbmail to use libzdb, and use prepared statements. But I can't seem to get prepared statements to work for postgresql. Sqlite and mysql work as expected by postgres keeps throwing exceptions. My test code reads: //URL_T url = \ URL_new("postgresql://localhost:5432/dbmail?user=dbmail&password=dbmail"); URL_T url = URL_new("postgresql://dbmail:dbmail@localhost/dbmail"); ConnectionPool_T pool = ConnectionPool_new(url); Connection_T con = ConnectionPool_getConnection(pool); PreparedStatement_T p = Connection_prepareStatement(con, "SELECT * FROM dbmail_users WHERE userid=?"); THis keeps throwing exception at: Uncaught exception SQLException raised in Connection_prepareStatement at src/db/Connection.c:294 On the postgres side all I see is: 2008-02-23 09:46:48 CET DEBUG: parse 1804289383: SELECT * FROM dbmail_users WHERE userid=$1 2008-02-23 09:46:48 CET DEBUG: StartTransactionCommand 2008-02-23 09:46:48 CET DEBUG: StartTransaction 2008-02-23 09:46:48 CET DEBUG: name: unnamed; blockState: DEFAULT; state: INPROGR, xid/subid/cid: 2270118/1/0, nestlvl: 1, children: <> 2008-02-23 09:46:48 CET DEBUG: CommitTransactionCommand 2008-02-23 09:46:48 CET DEBUG: CommitTransaction 2008-02-23 09:46:48 CET DEBUG: name: unnamed; blockState: STARTED; state: INPROGR, xid/subid/cid: 2270118/1/1, nestlvl: 1, children: <> 2008-02-23 09:46:48 CET LOG: unexpected EOF on client connection Any ideas? -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl

2 8

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

libzdb-general February 2008