Re: Bound column and serial datatype question - Mailing list pgsql-odbc

From Marko Ristola
Subject Re: Bound column and serial datatype question
Date
Msg-id 4269F1C7.7090906@kolumbus.fi
Whole thread Raw
In response to Bound column and serial datatype question  (lothar.behrens@lollisoft.de)
Responses Re: Bound column and serial datatype question
List pgsql-odbc
If you remove the NOT NULL definition from the CustomerNr,
you can put there a NULL value too.

The SQL email list is better for these questions, because they have
more knoledge of these kinds of problems ...

(The CustomerNr and ID columns seem to have redundant information.)

Regards,
Marko Ristola

lothar.behrens@lollisoft.de wrote:

>Hi,
>
>I have a table like this:
>
>CREATE TABLE Kunden
>(
>  ID serial NOT NULL,
>  CustomerNr serial NOT NULL,
>  Name CHAR(100),
>  ...
>);
>
>Using bound columns in a form to show the customer data I don´t like to let the user
>updating the CustomerNr field. This is because, a normal data field is not
>autogenerated, but these 'serial' data fields.
>
>But I like to show the CustomerNr field in the form. Therefore, I simply made the
>field readonly in the form. But if I insert a new row, the fields data (defaults to 0)
>would be used as the new value in the table.
>
>How to avoid this ?
>
>Thanks
>
>Lothar
>
>--
>Lothar Behrens        www.lollisoft.de
>Rosmarinstr 3        My public project:
>40235 Düsseldorf      http://sourceforge.net/projects/lbdmf
>
>
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 8: explain analyze is your friend
>
>


pgsql-odbc by date:

Previous
From: Marko Ristola
Date:
Subject: Re: Another post 7.3.02 bug Was: ODBC and encodings problem
Next
From: "Joel Fradkin"
Date:
Subject: Re: [PERFORM] Joel's Performance Issues WAS : Opteron vs Xeon