[SQL] getting back autonumber just inserted

[mail TechEvolution]

hello

i ame a newbie to PostGreSQL, I ame using PostGreSQL 8.0 
(windowsinstaller) on a xp prof platform


i would like to get back the autonumber from the last record inserted, 
for other SQL db (m$ sql db ...) i could use:

SELECT @@ IDENTITY

can someone help me by informing me what the SQL syntax is to be used 
with PostGreSQL db and get the same result, the last autonumber inserted?


greeTz

wes

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [SQL] getting back autonumber just inserted

[Alvaro Herrera]

On Thu, Jul 07, 2005 at 07:50:16PM +0200, mail TechEvolution wrote:
> hello
> 
> i ame a newbie to PostGreSQL, I ame using PostGreSQL 8.0 
> (windowsinstaller) on a xp prof platform
> 
> i would like to get back the autonumber from the last record inserted, 
> for other SQL db (m$ sql db ...) i could use:
> SELECT @@ IDENTITY
> 
> can someone help me by informing me what the SQL syntax is to be used 
> with PostGreSQL db and get the same result, the last autonumber inserted?

You use the currval() function, using the name of the involved sequence
as parameter.  There is a pg_get_serial_sequence() function, to which
you give the table name and column name, and it will give you the
sequence name.

-- 
Alvaro Herrera ()
Oh, oh, las chicas galacianas, lo harán por las perlas,
¡Y las de Arrakis por el agua! Pero si buscas damas
Que se consuman como llamas, ¡Prueba una hija de Caladan! (Gurney Halleck)

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly

Re: [SQL] getting back autonumber just inserted

[mail TechEvolution]

hi Alvaro Herrera


You use the currval() function, using the name of the involved sequence
as parameter.  There is a pg_get_serial_sequence() function, to which
you give the table name and column name


thx for the information

and is there a function i can use to get the last added autonumber without 
knowing wich table or row? (exactly as select @@ IDENTITY does?) i have read in 
the messages that there must be such a function for version 8.0, but i could 
not find it in the documentation, any idea on it?

greetZ

wes



Alvaro Herrera schreef:


On Thu, Jul 07, 2005 at 07:50:16PM +0200, mail TechEvolution wrote:
 


hello

i ame a newbie to PostGreSQL, I ame using PostGreSQL 8.0 
(windowsinstaller) on a xp prof platform


i would like to get back the autonumber from the last record inserted, 
for other SQL db (m$ sql db ...) i could use:

SELECT @@ IDENTITY

can someone help me by informing me what the SQL syntax is to be used 
with PostGreSQL db and get the same result, the last autonumber inserted?
   



You use the currval() function, using the name of the involved sequence
as parameter.  There is a pg_get_serial_sequence() function, to which
you give the table name and column name, and it will give you the
sequence name.

 




---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings

Re: [SQL] getting back autonumber just inserted

[Alvaro Herrera]

On Thu, Jul 07, 2005 at 08:21:12PM +0200, mail TechEvolution wrote:
> hi Alvaro Herrera
> 
> >>You use the currval() function, using the name of the involved sequence
> >>as parameter.  There is a pg_get_serial_sequence() function, to which
> >>you give the table name and column name
> 
> thx for the information
> 
> and is there a function i can use to get the last added autonumber without 
> knowing wich table or row? (exactly as select @@ IDENTITY does?) i have 
> read in the messages that there must be such a function for version 8.0, 
> but i could not find it in the documentation, any idea on it?

There is no such function in 8.0.  There will be in 8.1, however.

-- 
Alvaro Herrera ()
"El hombre nunca sabe de lo que es capaz hasta que lo intenta" (C. Dickens)

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq

Re: [SQL] getting back autonumber just inserted

[Theodore Petrosky]

you have to use currval inside a transaction...

begin;
insert something that increments the counter;
select currval('sequence_name');
end;

using currval inside a transaction guarantees that the
value is correct for your insert statement and has not
changed by another insert statement.

Ted


--- mail TechEvolution <[EMAIL PROTECTED]> wrote:

> hello
> 
> i ame a newbie to PostGreSQL, I ame using PostGreSQL
> 8.0 
> (windowsinstaller) on a xp prof platform
> 
> i would like to get back the autonumber from the
> last record inserted, 
> for other SQL db (m$ sql db ...) i could use:
> SELECT @@ IDENTITY
> 
> can someone help me by informing me what the SQL
> syntax is to be used 
> with PostGreSQL db and get the same result, the last
> autonumber inserted?
> 
> greeTz
> 
> wes
> 
> ---(end of
> broadcast)---
> TIP 4: Don't 'kill -9' the postmaster
> 





Sell on Yahoo! Auctions – no fees. Bid on great items.  
http://auctions.yahoo.com/

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Re: [SQL] getting back autonumber just inserted

[Scott Marlowe]

On Thu, 2005-07-07 at 15:14, Theodore Petrosky wrote:
> you have to use currval inside a transaction...
> 
> begin;
> insert something that increments the counter;
> select currval('sequence_name');
> end;
> 
> using currval inside a transaction guarantees that the
> value is correct for your insert statement and has not
> changed by another insert statement.

Actually, whether you use it inside a transaction or not, as long as
it's in the same session / connection, it is guaranteed to "do the right
thing."

Test it, you'll see.

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly

Re: [SQL] getting back autonumber just inserted

[mail TechEvolution]

THX to all guys, it is working great !!

greetZ

wes

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
   (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Re: [SQL] getting back autonumber just inserted

[Michael Fuhr]

On Thu, Jul 07, 2005 at 01:14:33PM -0700, Theodore Petrosky wrote:
> 
> you have to use currval inside a transaction...

Not true.  Have you observed otherwise?

> begin;
> insert something that increments the counter;
> select currval('sequence_name');
> end;
> 
> using currval inside a transaction guarantees that the
> value is correct for your insert statement and has not
> changed by another insert statement.

currval() returns the most recently obtained value from the sequence
in the current session, regardless of what other sessions are doing
or whether the current session is in a transaction.  See the
documentation and the FAQ:

http://www.postgresql.org/docs/8.0/static/functions-sequence.html

"Notice that because this is returning a session-local value, it
gives a predictable answer whether or not other sessions have
executed nextval since the current session did."

http://www.postgresql.org/docs/faqs.FAQ.html#4.11.3

"4.11.3) Doesn't currval() lead to a race condition with other users?

"No.  currval() returns the current value assigned by your session, not by
all sessions."

You can do experiments to confirm what the documentation states.
If you see different behavior then please put together a self-contained
test case and report it as a bug.

-- 
Michael Fuhr
http://www.fuhr.org/~mfuhr/

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [SQL] getting back autonumber just inserted

[Michael Fuhr]

On Thu, Jul 07, 2005 at 02:47:23PM -0600, Larry Meadors wrote:
>
> If you have a trigger on your table that inserts a record in a table
> and shares the same sequence, what value do you get back, the
> triggered curval, or the currently inserted one?

That's a different issue than whether currval() is subject to
interference from other transactions.  And just wait until PostgreSQL
8.1 comes out and people start using lastval() -- then it could get
*really* confusing which sequence value you're getting.

-- 
Michael Fuhr
http://www.fuhr.org/~mfuhr/

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Re: [SQL] getting back autonumber just inserted

[PFC]

That's a different issue than whether currval() is subject to
interference from other transactions.  And just wait until PostgreSQL
8.1 comes out and people start using lastval() -- then it could get
*really* confusing which sequence value you're getting.


	What happens if an INSERT trigger inserts something into another table  
which also has a sequence ?



---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [SQL] getting back autonumber just inserted

[Alvaro Herrera]

On Fri, Jul 08, 2005 at 12:26:30AM +0200, PFC wrote:
> 
> >That's a different issue than whether currval() is subject to
> >interference from other transactions.  And just wait until PostgreSQL
> >8.1 comes out and people start using lastval() -- then it could get
> >*really* confusing which sequence value you're getting.
> 
>   What happens if an INSERT trigger inserts something into another 
>   table  which also has a sequence ?

Using what, lastval()?  The app will get very confused, because it'll
get the value from the sequence used in the trigger.  Using currval
there is no problem, but you already knew that.

-- 
Alvaro Herrera ()
"Hay quien adquiere la mala costumbre de ser infeliz" (M. A. Evans)

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [SQL] getting back autonumber just inserted

[Michael Fuhr]

On Fri, Jul 08, 2005 at 12:26:30AM +0200, PFC wrote:
> 
> >That's a different issue than whether currval() is subject to
> >interference from other transactions.  And just wait until PostgreSQL
> >8.1 comes out and people start using lastval() -- then it could get
> >*really* confusing which sequence value you're getting.
> 
> What happens if an INSERT trigger inserts something into another 
> table  which also has a sequence ?

Do you mean with lastval()?  Here's what happens:

CREATE FUNCTION trigfunc() RETURNS trigger AS $$
BEGIN
INSERT INTO bar (x) VALUES (NEW.x);
RETURN NEW;
END;
$$ LANGUAGE plpgsql VOLATILE;

CREATE TABLE foo (id serial PRIMARY KEY, x integer);
CREATE TABLE bar (id serial PRIMARY KEY, x integer);

CREATE TRIGGER footrig BEFORE INSERT ON foo
  FOR EACH ROW EXECUTE PROCEDURE trigfunc();

ALTER SEQUENCE bar_id_seq RESTART WITH 50;

INSERT INTO foo (x) VALUES (12345);

SELECT lastval();
 lastval 
-
  50
(1 row)

SELECT * FROM foo;
 id |   x   
+---
  1 | 12345
(1 row)

SELECT * FROM bar;
 id |   x   
+---
 50 | 12345
(1 row)

-- 
Michael Fuhr
http://www.fuhr.org/~mfuhr/

---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings

[SQL] Make COUNT(*) Faster?

[Varun Mehta]

Hello all you PostgreSQL/SQL gurus!

I've started using PostgreSQL pretty recently, and I am quite  
disturbed about the performance of a simple SELECT COUNT(*) FROM  
table.  What should (in my mind) be a nearly instantaneous operation  
instead takes nearly 700ms in a table with only 87k rows of data!


If I run an EXPLAIN on this query I can see that it is doing a  
sequential scan, which seems quite needless, as surely this  
information is cached in some secret location.


It is very possible that I am missing something, so I ask you: is  
there a faster way to find out how many rows are in a table?  I've  
tried doing a COUNT(column) where I have an index on column, but it  
still does a sequential scan and it is still very very slow.  What  
are my options?


I offer you many thanks in advance,
Varun Mehta

---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings

Re: [SQL] getting back autonumber just inserted

[PFC]

Do you mean with lastval()?  Here's what happens:


	Hm, interesting, you mean the return value of lastval() also depends if  
you set your constraints  to deferred or immediate ?

I wond

---(end of broadcast)---
TIP 6: Have you searched our list archives?

  http://archives.postgresql.org

Re: [SQL] getting back autonumber just inserted

[PFC]

What happens if an INSERT trigger inserts something into another
table  which also has a sequence ?


Using what, lastval()?  The app will get very confused, because it'll
get the value from the sequence used in the trigger.  Using currval
there is no problem, but you already knew that.


I knew but I forgot since I use an ORM which handles all the mess ;)



---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
  choose an index scan if your joining column's datatypes do not
  match

Re: [SQL] getting back autonumber just inserted

[Michael Fuhr]

On Fri, Jul 08, 2005 at 01:56:26AM +0200, PFC wrote:
> >Do you mean with lastval()?  Here's what happens:
> 
> Hm, interesting, you mean the return value of lastval() also depends 
> if  you set your constraints  to deferred or immediate ?

My mind's ablank trying to contrive a situation where that would
matter.  Can you provide an example?

In any case, I simply meant to point out that 8.1's lastval() will
be seductively convenient because you don't have to pass it a
sequence name, but the value it returns might not be the value you
want.

-- 
Michael Fuhr
http://www.fuhr.org/~mfuhr/

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match

Re: [SQL] Make COUNT(*) Faster?

[Michael Fuhr]

On Thu, Jul 07, 2005 at 03:48:39PM -0700, Varun Mehta wrote:
> 
> I've started using PostgreSQL pretty recently, and I am quite  
> disturbed about the performance of a simple SELECT COUNT(*) FROM  
> table.  What should (in my mind) be a nearly instantaneous operation  
> instead takes nearly 700ms in a table with only 87k rows of data!

Speeding up COUNT is on the developers' TODO list, but it's not as
simple as it might seem or it would have been done already.  This
has been brought up many times over the years -- search the archives
to see past discussion.  Words to search for include "MVCC," "index,"
and "visibility."

> If I run an EXPLAIN on this query I can see that it is doing a  
> sequential scan, which seems quite needless, as surely this  
> information is cached in some secret location.

If an estimate will suffice then you could use the table's
pg_class.reltuples value, but beware that it can be rather
out of date.

http://www.postgresql.org/docs/8.0/static/catalog-pg-class.html

-- 
Michael Fuhr
http://www.fuhr.org/~mfuhr/

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Re: [SQL] getting back autonumber just inserted

[PFC]

On Fri, Jul 08, 2005 at 01:56:26AM +0200, PFC wrote:

>Do you mean with lastval()?  Here's what happens:

Hm, interesting, you mean the return value of lastval() also depends
if  you set your constraints  to deferred or immediate ?


My mind's ablank trying to contrive a situation where that would
matter.  Can you provide an example?


	It's rather perverse and farfetched, but what would stop one from putting  
some insert statements in a function that happens to be called somewhere  
inside of a check constraint... although one could agree that it's a bit  
shooting oneself in the foot...



In any case, I simply meant to point out that 8.1's lastval() will
be seductively convenient because you don't have to pass it a
sequence name, but the value it returns might not be the value you
want.


It's the first time I see a MySQLism in postgres !
	However I like it, cos it might subvert some MySQL users, and provide  
easy answers to The Weekly Question on the mailing list (ie where is  
AUTO_INCREMENT) ?
	I've just noticed that I forgot a close() somewhere hence my data import  
files missed a few chunks at the end and MySQL said "3 warnings, 0 errors"  
(if it had failed I would have noticed it a week ago but no, more  
-00-00:00:00:00 hand pruning for me now). Uh oh, SHOW WARNINGS isn't  
implemented in that version. There are warnings, but I won't tell you  
where. Somewhere. Hm... grep logs ? yeah, but the error message doesn't  
mention the table name... nor what kind of warning it is that is not an  
error even though half of the row has stayed in an unclosed() file  
buffer...




---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [SQL] getting back autonumber just inserted

[Michael Fuhr]

On Fri, Jul 08, 2005 at 05:03:37AM +0200, PFC wrote:
> >On Fri, Jul 08, 2005 at 01:56:26AM +0200, PFC wrote:
> >>Hm, interesting, you mean the return value of lastval() also depends
> >>if  you set your constraints  to deferred or immediate ?
> >
> >My mind's ablank trying to contrive a situation where that would
> >matter.  Can you provide an example?
> 
> It's rather perverse and farfetched, but what would stop one from 
> putting  some insert statements in a function that happens to be called 
> somewhere  inside of a check constraint... although one could agree that 
> it's a bit  shooting oneself in the foot...

PostgreSQL doesn't support deferral of check constraints, only
foreign key constraints.  But yeah, if you could do that then
presumably lastval() might return a different sequence's value
depending on whether the constraints were deferred or immediate.

-- 
Michael Fuhr
http://www.fuhr.org/~mfuhr/

---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org

Re: [SQL] Make COUNT(*) Faster?

[Chris Browne]

[EMAIL PROTECTED] (Varun Mehta) writes:
> If I run an EXPLAIN on this query I can see that it is doing a
> sequential scan, which seems quite needless, as surely this
> information is cached in some secret location.

That would in fact surely *NOT* be the case.

If you have multiple users performing updates on that table
concurrently, with the possibility of some of those updates rolling
back, then it doesn't make sense for there to be any such "one place"
where a count would be stored.

Consider the case where you ask for COUNT(*) while the following set
of transactions are outstanding:

  1.  A transaction, which, as it turns out, will get rolled back,
  that has inserted 40 tuples;

  2.  A transaction which has modified 10 tuples, thereby generating
  10 dead tuples and adding 10 new ones;

  3.  14 transactions are outstanding, each of which have added
  2 tuples to the table.

None of those transactions have COMMITted, so there are some 78 tuples
"in limbo" spread across 16 transactions.

If there were some "single secret place" with a count, how would you
suggest it address those 78 tuples and 16 transactions that aren't yet
(and maybe never will be) part of the count?

> It is very possible that I am missing something, so I ask you: is
> there a faster way to find out how many rows are in a table?  I've
> tried doing a COUNT(column) where I have an index on column, but it
> still does a sequential scan and it is still very very slow.  What
> are my options?

Use of the index doesn't help because the index isn't forcibly up to
date.  It has no notion of marking "index tuples" as dead/not visible.
Visibility information is only attached to the tuples themselves.

Look up "MVCC" for more details...
-- 
(format nil "[EMAIL PROTECTED]" "cbbrowne" "acm.org")
http://www.ntlug.org/~cbbrowne/sap.html
Rules of the Evil Overlord #78.  "I will not tell my Legions of Terror
"And he must  be taken alive!" The command will be:  ``And try to take
him alive if it is reasonably practical.''"


---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match

Re: [SQL] Make COUNT(*) Faster?

[Tom Lane]

Chris Browne <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (Varun Mehta) writes:
>> If I run an EXPLAIN on this query I can see that it is doing a
>> sequential scan, which seems quite needless, as surely this
>> information is cached in some secret location.

> [ example scenario snipped ]
> If there were some "single secret place" with a count, how would you
> suggest it address those 78 tuples and 16 transactions that aren't yet
> (and maybe never will be) part of the count?

It's worse than that: once some of those transactions have committed,
the right answer is observer-dependent, since some onlooker transactions
may see those guys as committed while others think they are not yet
committed.  So there could certainly not be just one secret place...

There are solutions suggested in the archives, but they all amount
to making COUNT(*)-with-no-WHERE-or-GROUP-BY-clause fast at the price
of nontrivial distributed overhead for all updates --- overhead that
would be paid whether or not the application ever did such a COUNT.
That's not a tradeoff we've wanted to make in general.  You can
implement it yourself via triggers for specific tables that you think
it's worth doing for.

Also, if an approximate answer is good enough, there are a whole other
set of possible solutions.

regards, tom lane

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster

[SQL] two sums in one query

[Kenneth Gonsalves]

hi
i have a table like this:

serialno varchar,
debit integer,
credit integer,
amount numeric

the columns 'debit' and 'credit' refer to the acount number. I want to 
query the table to select all the rows where either debit = account 
or credit=account and to get two sums - one of the amounts where the 
account is on the debit side and the other on the credit side. Can i 
do this in one query? if so, how?
-- 
regards
kg

http://www.livejournal.com/users/lawgon
tally ho! http://avsap.org.in
ಇಂಡ್ಲಿನಕ್ಸ வாழ்க!

---(end of broadcast)---
TIP 6: explain analyze is your friend

list admin note:Fwd: RE: [SQL] two sums in one query

[Kenneth Gonsalves]

this guy is still polluting this list:

--  Forwarded Message  --

Subject: RE: [SQL] two sums in one query
Date: Friday 08 Jul 2005 11:33 am
From: AntiSpam UOL <[EMAIL PROTECTED]>
To: lawgon <[EMAIL PROTECTED]>



http://antispam.uol.com.br";
 style="font:bold 10px verdana; padding-left:5px;
 text-decoration:none; color:white;">ANTISPAM UOL »
 TIRA-TEIMA 




 
 
Olá,
Você enviou uma mensagem para 
[EMAIL PROTECTED]
Para que sua mensagem seja 
encaminhada, por favor, http://tira-teima.as.uol.com.br/challengeSender.html?data=dfj2
RcMRVAMqAqRQr%2BDFbnjriSBKRVpApCuYtIfJSjMZrzX24WJDqyl7oj4Zc0t49l5sMpU
V%2Bpou%0AvW59walwIaK82PYACcj3x9IPrAYt4yTtrn1Dkcf019y1Q7ILcRd6ZQQIp33
k%2BeNJwLSwFj4xIw%3D%3D" target=_blank>clique aqui
 

 



Esta 
confirmação é necessária porque
 [EMAIL PROTECTED] usa o Antispam UOL, um programa que
 elimina mensagens enviadas por robôs, como pornografia, propaganda e
 correntes. As próximas mensagens enviadas para
 [EMAIL PROTECTED] não precisarão ser
 confirmadas*. *Caso você receba outro pedido de
 confirmação, por favor, peça para [EMAIL PROTECTED] incluí-lo
 em sua lista de autorizados. Atenção! Se você não conseguir clicar no
 atalho acima, acesse este endereço:
 http://tira-teima.as.uol.com.br/challengeSender.html?data=dfj2RcMRVA
MqAqRQr%2BDFbnjriSBKRVpApCuYtIfJSjMZrzX24WJDqyl7oj4Zc0t49l5sMpUV%2Bpo
u%0AvW59walwIaK82PYACcj3x9IPrAYt4yTtrn1Dkcf019y1Q7ILcRd6ZQQIp33k%2BeN
JwLSwFj4xIw%3D%3D 




 



 
 
Hi,
You´ve just sent a message to 
[EMAIL PROTECTED]
In order to confirm the sent 
message, please http://tira-teima.as.uol.com.br/challengeSender.html?data=dfj2
RcMRVAMqAqRQr%2BDFbnjriSBKRVpApCuYtIfJSjMZrzX24WJDqyl7oj4Zc0t49l5sMpU
V%2Bpou%0AvW59walwIaK82PYACcj3x9IPrAYt4yTtrn1Dkcf019y1Q7ILcRd6ZQQIp33
k%2BeNJwLSwFj4xIw%3D%3D" target=_blank>click here
 

 



This 
confirmation is necessary
 because [EMAIL PROTECTED] uses Antispam UOL, a service
 that avoids unwanted messages like advertising, pornography,
 viruses, and spams. Other messages sent to
 [EMAIL PROTECTED] won't need to be confirmed*.
 *If you receive another
 confirmation request, please ask [EMAIL PROTECTED] to include
 you in his/her authorized e-mail list. Warning! If the
 link doesn´t work, please copy the address below and paste it on
 your browser:
 http://tira-teima.as.uol.com.br/challengeSender.html?data=dfj2RcMRVA
MqAqRQr%2BDFbnjriSBKRVpApCuYtIfJSjMZrzX24WJDqyl7oj4Zc0t49l5sMpUV%2Bpo
u%0AvW59walwIaK82PYACcj3x9IPrAYt4yTtrn1Dkcf019y1Q7ILcRd6ZQQIp33k%2BeN
JwLSwFj4xIw%3D%3D 





Use o http://antispam.uol.com.br";>AntiSpam UOL e proteja sua caixa
 postal 


RdFhCfCggWeb =
 '1996-';http://indice.uol.com.br/anouol.js";>
 

---

-- 
regards
kg

http://www.livejournal.com/users/lawgon
tally ho! http://avsap.org.in
ಇಂಡ್ಲಿನಕ್ಸ வாழ்க!

---(end of broadcast)---
TIP 6: explain analyze is your friend

Re: [SQL] PostgreSQL and Delphi 6

[Mathew Winters]

I am a bit late posting, I use Zeos DBO controls, they can be found on 
sourceforge..


I actually use the V5 of the components with some bug fixes I done 
myself, but my project is too far along to change to the newer components..


They are free and all source provided.. :)

Postgres Admin wrote:

I have a client who wants to use Delphi as a front end to a Database, I
would like to use PostgreSQL over MSSQL and have been looking at the
psqlodbc project.  Will psqlodbc connect with Delphi 6? Basically, I'm
wondering if anyone has experience with it?   Any help will be appreciated.

Thanks,
J


---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
  joining column's datatypes do not match



---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings