Received: from mail.postgresql.org (webmail.postgresql.org [216.126.85.28]) by mail.postgresql.org (8.11.1/8.11.1) with SMTP id f2DEQKx25969 for ; Tue, 13 Mar 2001 09:26:20 -0500 (EST) (envelope-from pgsql-sql-owner@postgresql.org) Received: from home.grafton.lv (home.grafton.lv [159.148.106.93]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f2CDlox09913 for ; Mon, 12 Mar 2001 08:47:51 -0500 (EST) (envelope-from emils@grafton.lv) Received: from localhost (home.grafton.lv [127.0.0.1]) by home.grafton.lv (8.9.3/8.8.7) with SMTP id PAA04265 for pgsql-sql@postgresql.org; Mon, 12 Mar 2001 15:46:26 -0200 Date: Mon, 12 Mar 2001 15:46:26 -0200 From: emils@mail.grafton.lv Message-Id: <200103121746.PAA04265@home.grafton.lv> Organization: Grafton Entertainment Subject: default value syntax - pg compared to? X-Archive-Number: 200103/255 X-Sequence-Number: 1914 Hello, 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 . Eg. CREATE TABLE test ( id integer default 5, fld1 text ); INSERT INTO test (fld1) VALUES ('blahblah'); So, is there any sqlserver that under these conditions will NOT make id = 5 for the inserted row? Background: There is a package called phprojekt where the developer has created some workarounds for different handlings of auto- incrementing fields (sequences) for the above databases. The only place he uses them, however, is in the INSERT stataments (and he does not need to know the new id value for the inserted row). So I suggested he rewrite INSERTs explicitly specifying field names and excluding the id field, rather than putting a server- specific "default value" token (which postgres does not support anyway). Will it work for the above other dbs? TIA for answers! Emils