> 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
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
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.
The thrust of this issue is that we are rolling out
a PostgreSQL database which is driven
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 t
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
On Wed, 30 Jun 1999, Herbert Liechti wrote:
> 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 t
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
--
~
Hi!
I've been trying to get postgres LO interface to work with python.
I have been successful with three configurations:
1) pgsql 6.4.2 & PyGreSQL 2.2 on Linux/x86
2) pgsql 6.5beta1 & PyGgeSQL 2.3 on Linux/x86
3) pgsql 6.5beta1 & PyGreSQL 2.3 on SPARC/Solaris 2.6
And failed with all other:
* 6
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, ap.age
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, agent
On Wed, Jun 30, 1999 at 01:44:05PM -0700, Stephen Boyle wrote:
>
> 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:
>
A little digging around reveals the cor
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 Inc
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
en
13 matches
Mail list logo
