[Libdbi-drivers-devel] pgsql error codes

2008-11-17 Thread Emmanuel Courrèges
Hello,
Currently with the PostgreSQL driver, there seems to be no way to get 
the error code string in the form: 
http://www.postgresql.org/docs/8.1/static/errcodes-appendix.html

dbi_conn_error() always returns 0, and the error message returned is 
just the Postgresql error message which is localized (french for me).
I would greatly appreciate if we could change this to error code - 
error message for example, so at least the error would be parsable even 
if the message is localized in any language, also you wouldn't have to 
parse full text.

How does the acceptance process for the change work?
Should I do the change?
Basically I don't want to run on a lib-dbi-drivers that would be patched 
by me, I'd rather have it in the official branch.

Regards,
Emmanuel Courreges.

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
Libdbi-drivers-devel mailing list
Libdbi-drivers-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libdbi-drivers-devel


Re: [Libdbi-drivers-devel] [libdbi-users] libdbi 1.0, plan to launch

2008-11-17 Thread João Henrique Freitas
 I assume that the Makefile.am does not yet take into account that the
 headers were moved into include/cgreen. João, could you please fix
 these problems and verify the build with a fresh checkout?


Ok,

Please checkout the Branch-2008-11-11-cgreen. I fixed Makefile.am to
include cgreen headers.

Tested on a fresh instalation and checkout.
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
Libdbi-drivers-devel mailing list
Libdbi-drivers-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libdbi-drivers-devel


Re: [Libdbi-drivers-devel] [libdbi-users] libdbi 1.0, plan to launch

2008-11-17 Thread Markus Hoenicka
João Henrique Freitas writes:
  Please checkout the Branch-2008-11-11-cgreen. I fixed Makefile.am to
  include cgreen headers.
  

Thanks for fixing the remaining build problems. A fresh checkout now
compiles fine on my box. I still do get some make check failures which
I'd like to discuss. As your tests may be more sensitive than the old
ones, we may actually have to fix the drivers rather than the tests
:-)

The test results are appended below for reference. In brief, I
ran into the following problems:

- the get_string_copy and bind_string_copy tests may have a problem
because they fail in all drivers that execute this test. I can't
recall having problems with these functions using the old tests

- retrieving zero rows from mysql returns 25 rows?

- pgsql apparently fails to drop the database after each test, thus
causing each test to fail

- this interestingly causes make check to return Pass!

- the field_is_null and field_is_null_idx tests fail on sqlite and
  sqlite3. We'll have to check whether this is a driver or a test
  issue

- if firebird is fed with an incorrect username or password, the test
  app dumps core (it may do so with other drivers as well, didn't
  try). This is not the kind of graceful exit that we should strive
  for.

- firebird apparently has the same problem as pgsql in that the test
  app does not succeed in dropping the database between tests

I'd greatly appreciate if others could report their success stories
with the new test harness. I see a lot of potential in it, and I'm
glad João got this far at all, but there are still some rough edges
which keep me from switching over right away.

regards,
Markus

FreeBSD yeti.mininet 6.1-RELEASE FreeBSD 6.1-RELEASE #1: Mon Aug 28 22:24:48 
CEST 2006 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/YETI  i386

libdbi latest cvs revision
libdbi-drivers Branch-2008-11-11-cgreen

mysql:
Failure!: LIBDBI fixture - Retriving fields data by name - 
test_dbi_result_get_string_copy - [ERROR] should match [Can 'we' quote this 
properly?] at [test_dbi_retrieving_fields_data_name.c] line [336]
Failure!: LIBDBI fixture - Retriving fields data by name - 
test_dbi_result_bind_string_copy - [ERROR] should match ['Can 'we' quote 
this properly?'] at [test_dbi_retrieving_fields_data_name.c] line [1169]
Failure!: LIBDBI fixture - Test select cases - test_retrieve_zero_rows - 
[25] should match [0] at [test_dbi_misc.c] line [13]
Completed libdbi tests: 410 passes, 3 failures, 0 exceptions.
FAIL: test_dbi

pgsql:
Running libdbi tests...
NOTICE:  CREATE TABLE will create implicit sequence test_datatypes_id_seq for 
serial column test_datatypes.id
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index 
test_datatypes_pkey for table test_datatypes
Exception!: LIBDBI fixture - Database Infrastructure - 
test_dbi_conn_select_db - Test test_dbi_conn_select_db failed to complete
Database not created.
Darn! Can't create database! Error message: ERROR:  database 
libdbitest already exists
[repeated dozens of times]
Completed libdbi tests: 0 passes, 0 failures, 93 exceptions.
PASS: test_dbi (sic!)

sqlite:
Failure!: LIBDBI fixture - Retrieving fields meta-data - 
test_dbi_result_field_is_null - [0] should match [1] at 
[test_dbi_retrieving_fields_metadata.c] line [562]
Failure!: LIBDBI fixture - Retrieving fields meta-data - 
test_dbi_result_field_is_null_idx - [0] should match [1] at 
[test_dbi_retrieving_fields_metadata.c] line [582]
Failure!: LIBDBI fixture - Retriving fields data by name - 
test_dbi_result_get_string_copy - [ERROR] should match [Can 'we' quote this 
properly?] at [test_dbi_retrieving_fields_data_name.c] line [336]
Failure!: LIBDBI fixture - Retriving fields data by name - 
test_dbi_result_bind_string_copy - [ERROR] should match ['Can 'we' quote 
this properly?'] at [test_dbi_retrieving_fields_data_name.c] line [1169]
Failure!: LIBDBI fixture - Retriving fields as - 
test_dbi_result_get_as_string - [3.402823e+38] should match [3.402820e+38] at 
[test_dbi_retrieving_fields_as.c] line [234]
Completed libdbi tests: 469 passes, 5 failures, 0 exceptions.
FAIL: test_dbi

sqlite3:
Failure!: LIBDBI fixture - Retrieving fields meta-data - 
test_dbi_result_field_is_null - [0] should match [1] at 
[test_dbi_retrieving_fields_metadata.c] line [562]
Failure!: LIBDBI fixture - Retrieving fields meta-data - 
test_dbi_result_field_is_null_idx - [0] should match [1] at 
[test_dbi_retrieving_fields_metadata.c] line [582]
Failure!: LIBDBI fixture - Retriving fields data by name - 
test_dbi_result_get_string_copy - [ERROR] should match [Can 'we' quote this 
properly?] at [test_dbi_retrieving_fields_data_name.c] line [336]
Failure!: LIBDBI fixture - Retriving fields data by name - 
test_dbi_result_bind_string_copy - [ERROR] should match ['Can 'we' quote 
this properly?'] at [test_dbi_retrieving_fields_data_name.c] line [1169]
Failure!: LIBDBI fixture - Retriving fields as - 
test_dbi_result_get_as_string - [3.402823e+38] should match