Re: [GENERAL] how to change delimiter single-quote ?

1999-06-30 Thread Remigiusz Sokolowski
Hello I'have some problems with single-quote, if i insert some text with single-quote ( ' ) error occured !!! thanks The common way to achieve this is to double up the quotes: INSERT INTO table (column) VALUES ('Some ''quoted'' text'); I don't try it, but in such a cases I use

[GENERAL] Postgres Upsizing Tool for MSAccess 97

1999-06-30 Thread Stephen Boyle
Subject: Postgres Upsizing Tool for MSAccess 97 I have today set up a web page to allow download of pgupt. The tool written in Access 97 provides the following functionality: Creation of SQL / DDL statements to recreate database structure. Automatic creation of triggers in plpgsql to

[GENERAL] Default values not working

1999-06-30 Thread Bryan White
If I add a field to a colum using: alter table mytable add column myint int not null default 0; The default value does not seem to make it into the data dictionary. This is using Postgres 6.5. Is there is way to manually poke a default value into the data dictionary? Bryan White ArcaMax

[GENERAL] JOIN exclusion problem

1999-06-30 Thread Anja Speerforck
Hello, I'm trying to join three tables, where I need only one piece of data from two of the tables. The code I wrote is: SELECT apartner_nr, ap.anrede, ap.vorname, ap.nachname, ap.telefon, ap.fax, ap.email, ap.kunden_nr, k.name1, ap.agentur_nr, ag.name1 FROM ansprechpartner ap, kunden k,

Re: [GENERAL] JOIN exclusion problem

1999-06-30 Thread Peter Eisentraut
On Wed, 30 Jun 1999, Anja Speerforck wrote: Hello, I'm trying to join three tables, where I need only one piece of data from two of the tables. The code I wrote is: SELECT apartner_nr, ap.anrede, ap.vorname, ap.nachname, ap.telefon, ap.fax, ap.email, ap.kunden_nr, k.name1,

[GENERAL] urgent: problems with query_limit

1999-06-30 Thread Herbert Liechti
Hi We upgraded our system from 6.4 to the new 6.5 version. The set query_limit function is not working anymore in 6.5. db = set query_limit to '100'; SET VARIABLE db = select * from table; statement is returning all records from the table. What's wrong here? Herbie --

[GENERAL] Re: [INTERFACES] large objects

1999-06-30 Thread Tom Lane
Lauri Posti [EMAIL PROTECTED] writes: I've been trying to get postgres LO interface to work with python. I think you need begin/end transaction around lo_open ... lo_close sequence. regards, tom lane

RE: [GENERAL] urgent: problems with query_limit

1999-06-30 Thread Jackson, DeJuan
Try: select * from table LIMIT 100; Hi We upgraded our system from 6.4 to the new 6.5 version. The set query_limit function is not working anymore in 6.5. db = set query_limit to '100'; SET VARIABLE db = select * from table; statement is returning all records from the table. What's

Re: [HACKERS] RE: [GENERAL] urgent: problems with query_limit

1999-06-30 Thread Jan Wieck
Marcus "Mike" Mascari wrote: What I would like to see (perhaps its possible right now, or a workaround is available) is a method for yielding an elog() message when the number of tuples to be returned is over a specified USER limit. [...] However, what we would like to prevent is some

Re: [GENERAL] urgent: problems with query_limit

1999-06-30 Thread Bruce Momjian
Hi We upgraded our system from 6.4 to the new 6.5 version. The set query_limit function is not working anymore in 6.5. db = set query_limit to '100'; SET VARIABLE db = select * from table; statement is returning all records from the table. What's wrong here? Use the new LIMIT