Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f2CKIfx60056 for ; Mon, 12 Mar 2001 15:18:41 -0500 (EST) (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 23712; Mon, 12 Mar 2001 12:18:38 -0800 From: "Josh Berkus" Subject: Re: default value syntax - pg compared to? To: "Emils Klotins" , pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Mon, 12 Mar 2001 12:18:38 -0800 Message-ID: In-Reply-To: <3AA6231A.29527.13F907D2@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200103/228 X-Sequence-Number: 1887 Emils, > do you happen to know, if there is any sqlserver that WON'T handle > inserting default value if it is not specified in the INSERT field > list? > I am particularly interested in ORACLE, INFORMIX and MYSQL . MS SQL 6.5, 7.0 and 2000 all support default values on incremental fields ... with some caveats: 1. Unlike PostgreSQL, MSSQL server will not permit you to override an "Identity Value" auto-incrementing field; 2. MSSQL 6.5 and 7.0 do not support user-defined functions as default-values (or, for that matter, user-defined functions at all). Also, you should be aware that the pgODBC driver for Win32 clients does not recognize PostgreSQL sequences correctly when called as default vaues for other than a SERIAL field (i.e. if you use the DEFAULT NEXTVAL('sequence') construction rather than the SERIAL type, pgODBC will error out on INSERTS). -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