Use an sequence. Add the ID column to your create table statement and set
the default to use the next value from the sequence. This will give each
entry a unique id number. The syntax would be as follows.
create sequence customer_id start 1 increment 1 maxvalue 2147483647 minvalue
1 cache 1;
I browsed the FAQ and mailing list briefly to try to garner information
about the ups and downs of different character based datatypes. I did not
see any good document on preference or when to use one over the other.
http://postgresql.readysetnet.com/docs/faq-english.html#4.15 noted that
some co
> I browsed the FAQ and mailing list briefly to try to garner information
> about the ups and downs of different character based datatypes. I did not
> see any good document on preference or when to use one over the other.
>
> http://postgresql.readysetnet.com/docs/faq-english.html#4.15 noted th
I could give an insight on what Informix says about the difference between these
data types, I assume it applies to Postgres as well.
As the FAQ and mailing lists say, the CHAR datatype adds blank spaces to fill the
reserved space advantage: is faster when the data changes constantly; VARCHAR
So far I have only been able to get psql to start with these pg_hba.conf
entries:
localall
trust
host all 127.0.0.1 255.255.255.255 trust
Then, I can use
>psql -h localhost template1
and get a pro
[EMAIL PROTECTED] writes:
> Any other lines in pg_hba.conf don't seem to work,
Hmm. Forgive me for asking the obvious, but are you sure you are
editing the same copy of pg_hba.conf that the postmaster is looking at?
> Note I am using cygwin/NT 4.0 to run Postgres 7.0.3. I am
> starting and stop
