Vic,
Can you post the errors you are getting for both the build problem and
the runtime problem you originally reported?
Without the exact errors you are getting, I can only guess at the
problems you are encountering. But my guess as to your original problem
is that your code is trying to
If you are getting a parse error as you said in a latter message, then
you should set debug_print_query = true in your postgresql.conf file.
This will cause the sql statements to be printed in the server log
file and you then might be able to figure out why the statement sent
couldn't be
Graham,
I am guessing from the error that you are using JDBC as your client.
This looks like a known issue with the 7.0 jdbc driver. Have your tried
the 7.1 jdbc driver? (as long as you don't use the DatabaseMetadata
object too much, the 7.1 driver should work fine against a 7.0 database).
Culley,
With out more details of your setup, I can't give you a complete answer.
But check out the info at:
http://lab.applinet.nl/postgresql-jdbc/#CharacterEncoding
for a brief discussion of what I believe is your problem. There has
also been a number of discussions on this on the
Wieger,
The server does not have a concept of error codes currently (it is on
the TODO list). Therefore the JDBC driver has no error code to report
since it doesn't get one from the backend. When the server supports
error codes the JDBC driver will as well.
thanks,
--Barry
Wieger Uffink
FYI -- JDBC questions should go to the pgsql-jdbc mail list.
As for your problem, I think probably the easiest workaround is to
explicitly cast your constants. Assuming you are using
PreparedStatements, a statement of the following form should work:
select * from foo
where bar = ?::numeric
The behavior seen here seems correct although not intuitive. My guess
is that your database executables where created with locale support
enabled and your database was inited with a US locale. The sorting
logic for the english locales only sort on alpha-numeric characters.
All other
I ran into the same issue over the weekend. If you look in the
pgsql-ports email archives or the cygwin email archives you will see
that this is a known problem with cygwin 1.1.8. (I believe it is fixed
in current sources for cygwin). The workaround is to install cygwin
1.1.7. That solved
I am trying to call PL/pgSQL functions from JDBC via the Fastpath
interface. The function is executing but none of the arguments to the
function are getting set.
here is a simple example:
create function testcall (int4) returns int4 as '
begin
return $1;
end;
' language 'plpgsql';
In java I
I come from an Oracle background and am used to being able to parse a
query once and then rebind and reexecute that same query multiple
times. This can have huge performance benefits for frequently used
queries within an application.
I am new to PostgreSQL, and am trying to figure out how to do
10 matches
Mail list logo
