Matt, if u read what i said, i had it null b4, so the default value is on no consequence. And yes it can be null or I wouldn't be able to set it this way and NULL would not appear in the data. Also as I said, the field was set to 1, so it will not get defaulted to 0, this only happens when you do an insert and do not specify a value, it does not update columns to zero regardless of whether they contain data, this would be pointless.
-----Original Message----- From: Matt Horn [mailto:[EMAIL PROTECTED]] Sent: 09 August 2002 14:19 To: [EMAIL PROTECTED] Subject: Re: [ cf-dev ] update query if you dont specify that colunm it gets set to the default also bits are 0 or 1 they cannot be NULL At 14:08 09/08/02 +0100, you wrote: >ok check this out. > >I have a field in the table > >Admin bit default(0) > >The value of this field is currently set to 1 >I have just changed it to a NOT NULL value with a default, previous is a >NULL, still did the same thing. > >I run an update query, this query DOES NOT update this column. There are no >other update queries. Nothing touches this column at all. >Yet every time I run an update query, this field gets set to 0 all by >itself. >there are no triggers or anything of this sort to cause it, it is just a >plain old table. > > > >-- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] >For human help, e-mail: [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
