Akopia Akopia Services

[Date Prev][Date Next][Thread Prev][Thread Next][Minivend by date ][Minivend by thread ]

Re: [mv] (forw) Re: [ic] Interchange + PostgreSQL results in error 505's (premature end of script headers)



******    message to minivend-users from Mike Heins <mikeh@minivend.com>     ******

Quoting Warren Odom (warren-odom@stenocall.com):
> 
> >I still don't understand how NOT NULL works in Postgres, and no one
> >has been able to elucidate it. It appears to me that if you do
> >       INSERT (username,password) INTO userdb
> >       VALUES ('user', ");
> >that it will error out on NOT NULL. This is at odds with my understanding
> of how it should work; NOT NULL >appearse to be the moral equivalent of "NOT
> BLANK".
> 
> Although I haven't dived (yet) into getting MV/IC running with Postgres,
> your comment got me curious.  I know that in databases I've seen, NULL is
> separate and distinct from"blank".  Just to be sure, I created a test table
> in PG (I have version 6.5.3 on Red Hat) and set one of the columns "char
> varying(5) not null".  I was able to insert a zero-length string into that
> column using the above syntax (two single quotes placed together as in '').
> 

I removed all NOT NULL except password, tried Interchange, and it failed.
When I removed that last one, it worked.

UserDB does record-checking independently, therefore there should be no
need for NOT NULL settings in the database. I understand the use of NOT NULL
for referential integrity purposes, but in a database-independent
environment like Interchange it is difficult to deal with. This type
of checking is really designed for data-specific programming.

In the order database, the checking is done by profiles.

If someone can come up with a good reason why I should not specify no
NOT NULL in Interchange tables, I will certainly listen. But I cannot
see why we should have to worry about it.

Mike
-- 
Akopia, Inc., 131 Willow Lane, Floor 2, Oxford, OH  45056
phone +1.513.523.8220 fax 7501 <heins@akopia.com>

I have a cop friend who thinks he ought be able to give a new ticket;
"too dumb for conditions".
-
To unsubscribe from the list, DO NOT REPLY to this message.  Instead, send
email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
Archive of past messages: http://www.minivend.com/minivend/minivend-list


Search for: Match: Format: Sort by: