On 1/11/08, Rich Shepard <[EMAIL PROTECTED]> wrote:
> On Fri, 11 Jan 2008, P Kishor wrote:
>
> > it to PostGres (pain in the tush to develop with, but great to serve
>
> The actual name is PostgreSQL and it's usually referred to as postgres.
>
> > For example, why have the "INTEGER PRIMARY KEY" when it could just as
> > easily be called "SERIAL"?
>
> > One way might be to allow for aliases -- so, SERIAL would mean the
> > same as INTEGER PRIMARY KEY, or CHAR(3) would mean the same as TEXT
> > with a CHECK CONSTRAINT, and so on.
>
> From the PostgreSQL 8.1 docs:
>
> The data types serial and bigserial are not true types, but merely a
> notational convenience for setting up unique identifier columns (similar to
> the AUTO_INCREMENT property supported by some other databases). In the
> current implementation, specifying
>
> CREATE TABLE tablename (
> colname SERIAL
> );
>
> is equivalent to specifying:
>
> CREATE SEQUENCE tablename_colname_seq;
> CREATE TABLE tablename (
> colname integer DEFAULT nextval('tablename_colname_seq') NOT NULL
> );
>
> You can create your own.
>
yes, I understood all that from the docs. That was not the point of my
query. My query was on making "datatypes" and "aliases" to the said
"datatypes" in SQLite so they would match those available in
"postgres," complexifying SQLite notwithstanding.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
