The following bug has been logged online:
Bug reference: 3941
Logged by: gnp yadav
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Ubuntu Linux
Description:Insert Error
Details:
CREATE TABLE sentence
(
sentence_id serial NOT NULL,
cita
gnp yadav wrote:
The following bug has been logged online:
Bug reference: 3941
Logged by: gnp yadav
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Ubuntu Linux
Description:Insert Error
Details:
CREATE TABLE sentence
(
sentence_id seri
gnp yadav wrote:
The following bug has been logged online:
Bug reference: 3941
Logged by: gnp yadav
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Ubuntu Linux
Description:Insert Error
Details:
CREATE TABLE sentence
(
sentence_id seri
Valentine Gogichashvili wrote:
The following bug has been logged online:
Bug reference: 3942
Logged by: Valentine Gogichashvili
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
You should upgrade to the latest 8.2.X minor release, regardless of this
issue...
Op
The following bug has been logged online:
Bug reference: 3944
Logged by: Dan Hrabarchuk
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.0
Operating system: Linux, Fedora Core 8
Description:Unable to create a database using SQL_ASCII encoding
Details:
I can
The following bug has been logged online:
Bug reference: 3943
Logged by: Arnaud
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.0
Operating system: linux debian etch
Description:ecpg doesn't like "inet" operator
Details:
This is a sample of my C programm re
The following bug has been logged online:
Bug reference: 3942
Logged by: Valentine Gogichashvili
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: Linux 2.6.8 SMP
Description:Related to BUG #2568 and BUG #2859: VACUUM process hangs
and does
Pit M. wrote:
I had the same problem this morning. We provide a sample database with
LATIN1 encoding (included in our setup). So how can i change my encoding
to have a database that can be used with PG 8.1; 8.1; 8.2 and 8.3
without problems and without knowing how the server was installed? What
"Dan Hrabarchuk" <[EMAIL PROTECTED]> writes:
> I can not use SQL_ASCII encoding.
Use C locale.
regards, tom lane
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-
"Arnaud" <[EMAIL PROTECTED]> writes:
> EXEC SQL SELECT text(inet :ip_address) INTO :ip_result;
This is incorrect, and always has been, but 8.3 is more picky about it.
Use a cast instead, eg
> EXEC SQL SELECT text(:ip_address :: inet) INTO :ip_result;
regards, tom lane
Dan Hrabarchuk wrote:
How do I use standard ASCII? My legacy app in not compatible with unicode.
You can use the C-locale, see the user manual, section "22.1 Locale
Support" for more information:
http://www.postgresql.org/docs/8.3/interactive/locale.html
However, you don't have to use SQL_AS
11 matches
Mail list logo