Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f58M3IE92523 for ; Fri, 8 Jun 2001 18:03:18 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 69553; Fri, 08 Jun 2001 15:03:15 -0700 From: "Josh Berkus" Subject: Re: maximum number of rows in table - what about oid limits? To: Jonathan Bartlett , Josh Berkus Cc: pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Fri, 08 Jun 2001 15:03:15 -0700 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200106/136 X-Sequence-Number: 3357 Jon, > How exactly? The column types would just be INT8, right? Ah. I see what you mean. In my application, the columns are all *named* the same ... clients.usq, orders.usq, etc. Thus a search on "usq" through out the application will locate everything. If you needed and INT8 variable, you could define a custom type on INT8 ... and then search on that type. > Aha! The only thing I don't get is what do you mean by "execution > state"? > (I'm guessing that you're not referring to Texas). A variable indicating success or failure. e.g. In MSSQL, you get a ReturnValue of INT2 type ... with 0 indicating success, and <> 0 as an error number. Speaking of which, one thing I forgot to explicitly mention above is error trapping of some kind would be extremely useful ... -Josh Berkus ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco