[ic] Postgres + Debian error

[Peter]

On 01/08/2007 07:20 AM, Rene Hertell wrote:
> Peter wrote:
>> I think that for some reason it creates the row in the db with just the
>> username then uses an UPDATE to fill in the rest of the fields.
>> postgresql allows you to have a default of null for a NOT NULL field but
>> if you try to do an INSERT without specifying a value for that field
>> then you will end up with a NULL value error like you got.  Another way
>> to fix the problem would have been to change the password column to
>> default to '' (empty string) instead of NULL.  Actually changing it that
>> way will help with troubleshooting as well because it will tell us if
>> the field is being set to NULL by default or explicitly.
> 
> I tried to figure out if this was the case, but i could not locate the
> routine that would have done that..

ALTER TABLE userdb ALTER password SET DEFAULT '';

> I also get more errors, now in the UI and with the menu-editor:
> 
> set_slice error as called by Safe::Hole: DBD::Pg::st execute failed:
> ERROR: duplicate key violates unique constraint "tree_pkey" query
> was:insert into tree
> (code,mgroup,msort,next_line,indicator,exclude_on,depends_on,page,form,name,super,inactive,description,help_name,img_dn,img_up,img_sel,img_icon,url,member,parent_fld)
> VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) values
> were:'60','catalog/top','1','','','','','process/locale/de_DE/index','','Deutsch','','0','Select
> German','','','','','','','',''

It's saying that there was already a record in the table with a code of
60.  Did you maybe copy an existing dataset over but not reset the
counter file to a high enough number to start new records above the
existing ones?

Peter