X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 78DAAD1B906 for ; Tue, 9 Mar 2004 14:54:10 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 52086-01 for ; Tue, 9 Mar 2004 10:54:08 -0400 (AST) Received: from web60805.mail.yahoo.com (web60805.mail.yahoo.com [216.155.196.68]) by svr1.postgresql.org (Postfix) with SMTP id 3951CD1CA83 for ; Tue, 9 Mar 2004 10:54:03 -0400 (AST) Message-ID: <20040309145359.79236.qmail@web60805.mail.yahoo.com> Received: from [64.81.205.234] by web60805.mail.yahoo.com via HTTP; Tue, 09 Mar 2004 06:53:59 PST Date: Tue, 9 Mar 2004 06:53:59 -0800 (PST) From: ow Subject: Re: currval() without specifying the sequence name To: Achilleus Mantzios Cc: pgsql-sql@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/82 X-Sequence-Number: 17181 --- Achilleus Mantzios wrote: > > You could use the same sequence in many tables. > I guess I could but then: 1) I'd still have to know the sequence name. When integrating pgSql with 3party frameworks I'd either have to pass it there (could be a very difficult task) or make some assumptions (also not very good). 2) There may be a need to have different sequences being used in an app. 3) If one sequence is used, in many cases it'll have to be of type int8 and pgSql does not handle searches with int8 very nicely. Thanks __________________________________ Do you Yahoo!? Yahoo! Search - Find what you’re looking for faster http://search.yahoo.com