l,
NULL::text,
NULL::text,
'test'::text
);
Hope you can help me one more time. Thanks.
Regards,
Pit
On Tue, Oct 30, 2007 at 01:12:41PM +0100, Pit M. wrote:
Hi David!
Thanks for the fast reply. So you mean that I might already have
created a connection but am still trying
D...") and in the dbi-odbc documents I can't find any information
about the correct use of the parameters for the ODBC-connection. That's
why I tried to create the connection so many times.
Regards,
Pit
David Fetter wrote:
On Mon, Oct 29, 2007 at 03:44:05PM +0100, Pit M.
I have the following problem with PostgreSQL and hope you guys can help
me out in this matter: I try to get a remote connection to any database
(e.g. MS-SQL or MS Access) using DBI-Link and DBD:ODBC. My problem is,
that everything seems fine so far, however I don't know how to use the
parameter
On Mon, Jun 11, 2007 at 03:28:22PM +0200, Pit M. wrote:
We handle exceptions errors through libpq, and if a FETCH leads to such
a runtime error, we try to FETCH the first record again.
The problem is that we can't use this cursor any more -> it seems to be
corrupt after that err
Thank you Pavel!
The problem is, that the CAST function may be used in any SQL query,
since our software allows using a free SQL-query. The query itself
doesn't fail, because the syntax is correct.
The problem is that there may be other functions in a query that can
lead to a runtime error dur
I didn't try myself, but wrapping the whole into a PL/pgSQL function and
using exceptions might do the work;
http://www.postgresql.org/docs/8.2/static/plpgsql-control-structures.html#PLPGSQL-ERROR-TRAPPING
Ciao,
Thomas
Unfortunately this is not possible, because this should happen on the
cl
Pavel Stehule schrieb:
Hello
I thing so problem is there
AND Cast("CUSTOMERS"."ZIP" as integer) < 2
You cannot cast 'A1234' to integer
Regards
Pavel Stehule
Yes i know that i can't, but why the transaction fails?
Pit
---(end of broadcast)
We use PG 8.2.4 with as cursors over libpq and get an error:
ERROR: current transaction is aborted, commands ignored until end of
transaction block
How can we avoid this error or make the cursor still working afterwards?
Assume following contents of table CUSTOMERS:
ID | ZIP (varchar
Alexander Scholz wrote:
Yes, we have the same problem! Refer to the thread with the subject
"Problem V8.1.4 - providing pwd for commandline tools doesn't work anymore".
They seem to have change the old behaviour of the commandline tools,
which worked well since 8.0! I don't understand why the c
Which function of libpq.dll should one use to determine if a field may
contain NULL values ?
---(end of broadcast)---
TIP 6: explain analyze is your friend
Building without ENABLE_THREAD_SAFETY=1 works fine, but when i add this
option to the win32.mak some compiler error occur.
d:\postgresql-8.0.3\src\interfaces\libpq\libpq-int.h(481) : error
C2143: syntax error : missing ')' before '*'
d:\postgresql-8.0.3\src\interfaces\libpq\libpq-int.h(481) : erro
Is the standard libpq.dll distributed by PostgreSQL8.0 for windows
thread safe by default ?
Pit
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
12 matches
Mail list logo
