On Sun, Feb 27, 2000 at 07:35:13PM -0800, Seth Banks wrote:
> Anyone see a problem with this code?!
Yep - declaring a constaint of "NULL" is not standards compliant SQL: allowing
a column to be null _is_ the default in the standard. Just delete the NULL
from url, priority and content, and you should be fine.
Ross
--
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005
>
> CREATE TABLE content (
> content_id serial,
> parent_id int4 NOT NULL,
> parent_type int4 NOT NULL,
> author_id int4 NOT NULL,
> title text NOT NULL,
> url text NULL,
> start_date date NOT NULL,
> end_date date NOT NULL,
> priority int4 NULL,
> content text NULL,
> source text NOT NULL
> );
> ERROR: parser: parse error at or near "null"
>
> ************
>
