Hi,
I solved...
To create a trigger we don't need to change term. Just query the trigger like:
snprintf(ptr_cinfo-createsubschema[3], QUERY_LEN,
CREATE TRIGGER T1_BI FOR TEST_DATATYPES ACTIVE BEFORE INSERT
POSITION 0
AS
BEGIN
if (NEW.ID is NULL) then
João Henrique Freitas writes:
My first question is: I can pass one query with many statements
together split by a semicolon? like above?
I didn't find a definitive answer to this question, but looking at the
Firebird API Guide makes me think the DSQL interface accepts only one
statement
Hi,
Firebird is my next round.
3) testing the firebird driver is a PITA. The old test code runs to
completion except for the final DROP TABLE test. The new test code
triggers a Fatal lock manager error: invalid lock id (X), errno:
83 error on my platform. According to what Google says
Hello
The test:
http://my.cdash.org/testDetails.php?test=1211908build=25032
Tell me the line 230 of test_dbi_retrieving_fields_as.c:
assert_string_equal(the_float_as_string, 3.402820e+38);
The Cgreen framework have asserts to calc double but not strings.
Numerical strings are compared
Hi,
The drivers (sqlite was also affected, besides sqlite3) did not set
the NULL property of fields containing NULL. I've fixed this in
CVS. Could you please repeat your tests? Things seem to work ok here.
Ok, all fine.
Now I am working to solve this:
Failure!: sqlite3 - libdbi connection
Yes, please. I think we should support 8.0 for a while.
Ok, changing it...
I have other problem with sqlite3
The new test framework do following test functions
dbi_result_field_is_null and dbi_result_field_is_null_idx like:
-
result = dbi_conn_query(conn, SELECT
Quoting João Henrique Freitas joa...@gmail.com:
See http://www.postgresql.org/docs/current/static/sql-syntax-lexical.html
Item 4.1.2.1.
In test_dbi_cgreen.c:803 I use:
E'AB000C''D',
E'AB000C''D',
In pgsql 8.0 it is no supported.
May be I need to change it?
Yes, please. I
See http://www.postgresql.org/docs/current/static/sql-syntax-lexical.html
Item 4.1.2.1.
In test_dbi_cgreen.c:803 I use:
E'AB000C''D',
E'AB000C''D',
In pgsql 8.0 it is no supported.
May be I need to change it?
2009/5/1 Markus Hoenicka markus.hoeni...@mhoenicka.de:
João Henrique
Hello,
6) sqlite and sqlite 3 report 6 failures. Two stem from the
test_dbi_result_field_is_null(_idx) tests which may actually indicate
driver bugs. I'll look into that. The remainder are the problems
mentioned above.
I have a lot of failures with sqlite and sqlite3. Can you retest with
Hello,
5) pgsql complains about 'type e does not exist' when inserting data
into the table. This is apparently caused by the strings which you use
to fill the blob fields. What is the leading non-quoted 'E' intended
for?
What is our postgresql version?
Thanks
--
10 matches
Mail list logo
