Re: [HACKERS] Database object names and libpq in UTF-8 locale on Windows

Tom, Andrew, We have the same issue in our product: Support UTF-8 on Windows. You know certainly that UTF-8 code page (65001) is no supported by MS Windows when you set the locale with setlocale(). You cannot rely on standard libc functions such as isalpha(), mbtowc(), mbstowc(), wctomb(), wcsto

Re: [HACKERS] Database object names and libpq in UTF-8 locale on Windows

Hi all, I would appreciate some help or comments on this topic... Is this the wrong mailing list to ask such question? Seb On 10/18/2012 10:15 AM, Sebastien FLAESCH wrote: Hello, Using PostgreSQL 9.2.1 on Windows, I am facing a strange character set issue with a UTF-8 database. Maybe this is

[HACKERS] Database object names and libpq in UTF-8 locale on Windows

tool gives me "UNICODE" - is this the same as "UTF-8"?) So is there a bug, or do I have to use a C collation and char type for UTF-8 databases on Windows? I know that UTF-8 is not supported by the Windows C/POSIX library (setlocale, and co). Does it mean that it's not

[HACKERS] Database object names and libpq in UTF-8 locale on Windows

tool gives me "UNICODE" - is this the same as "UTF-8"?) So is there a bug, or do I have to use a C collation and char type for UTF-8 databases on Windows? I know that UTF-8 is not supported by the Windows C/POSIX library (setlocale, and co). Does it mean that it's not

Re: [HACKERS] [GENERAL] INTERVAL SECOND limited to 59 seconds?

operators and functions) are not 100% SQL99, but they are close... Thanks a lot! Seb Tom Lane wrote: Sebastien FLAESCH writes: I would expect that an INTERVAL SECOND can store more that 59 seconds. I took a look into the SQL spec and I think that we do indeed have a spec compliance issue here

[HACKERS] INTERVAL data type and libpq - what format?

Hello, I try to use the new 8.4 INTERVAL type with libpq, but get crazy with the input formatting rules... I use PQprepare() / PQexecPrepared() with parameter list, binding the INTERVAL values with the 1186 pg_type (is this ok?) and passing a string buffer with values like: "12345" for an INT

Re: [HACKERS] V8.3.0: PQprepare()/PQexecPrepared() and DECLARE CURSOR

2; test1=> open s1; test1=> prepare s1 as select * from dbit2; -- or PQprepare ( "s1" ) test1=> execute s1; As these are different objects for PostgreSQL - right? Seb Andrew Dunstan wrote: Sebastien FLAESCH wrote: For SQL producing a result set: PQprepare(... "cu1

Re: [HACKERS] V8.3.0: PQprepare()/PQexecPrepared() and DECLARE CURSOR

Sorry I should have double checked, it's my fault. I do not CLOSE the cursor before the third PQexecPrepare()... Never mind. Seb Sebastien FLAESCH wrote: Hi All, I am new to this mailing list and want to participate to the 8.3.0 beta program. (Sorry to be late BTW) My name is Seba

[HACKERS] V8.3.0: PQprepare()/PQexecPrepared() and DECLARE CURSOR

Hi All, I am new to this mailing list and want to participate to the 8.3.0 beta program. (Sorry to be late BTW) My name is Sebastien FLAESCH and I am in charge of the database interfaces at Four J's Development Tools. Our product is a Informix 4gl compatible compiler / runtime syste

Re: [HACKERS] PostgreSQL 8.3, libpq and WHERE CURRENT OF

sed. Seb Florian G. Pflug wrote: Sebastien FLAESCH wrote: Forget this one, just missing the WITH HOLD option... Must teach myself a bit more before sending further mails. Seb AFAIK you cannot use "WITH HOLD" together with updateable cursors. I might be wrong, tho

Re: [HACKERS] PostgreSQL 8.3, libpq and WHERE CURRENT OF

tips about the overhead/cost of moving to DECLARE CURSOR, it would help me a lot. Remember I am talking about a driver for our VM = moving to DECLARE CURSOR would apply to all SELECT statements used in an application. Thanks Seb Florian G. Pflug wrote: Sebastien FLAESCH wrote: Forget this one,

Re: [HACKERS] PostgreSQL 8.3, libpq and WHERE CURRENT OF

Forget this one, just missing the WITH HOLD option... Must teach myself a bit more before sending further mails. Seb Sebastien FLAESCH wrote: Ok... Tested with 8.2.3: Actually you can't DECLARE a cursor outside a transaction: test1=> declare c1 cursor for select * from dbit2; ERROR:

Re: [HACKERS] PostgreSQL 8.3, libpq and WHERE CURRENT OF

with ODBC cursors. Anyway, thanks for your help. Seb Tom Lane wrote: Sebastien FLAESCH <[EMAIL PROTECTED]> writes: Does a simple PQPrepare() with a SELECT statement not create a cursor on the server side? No. A prepared statement is just a query plan, not a query-in-progress. The Bind/

Re: [HACKERS] PostgreSQL 8.3, libpq and WHERE CURRENT OF

Tom Lane wrote: Sebastien FLAESCH <[EMAIL PROTECTED]> writes: Does a simple PQPrepare() with a SELECT statement not create a cursor on the server side? No. A prepared statement is just a query plan, not a query-in-progress. Yes of course, I meant PQprepare() + PQexecPrepared() ...

Re: [HACKERS] PostgreSQL 8.3, libpq and WHERE CURRENT OF

pare() with a SELECT statement not create a cursor on the server side? If yes, would it not be possible to pass a cursor name as in ODBC? Best regards, Seb Heikki Linnakangas wrote: Sebastien FLAESCH wrote: Just looked at the new features of 8.3 and realized that positioned updates/deletes is now po

[HACKERS] PostgreSQL 8.3, libpq and WHERE CURRENT OF

pment Tool vendor and have a bunch of customers migrating legacy applications from Informix to PostgreSQL... Thanks a lot! Sebastien FLAESCH Database Interfaces Four J's Development Tools ---(end of broadcast)--- TIP 9: In versions below 8.0, t