As a former Oracle developer, I decided to start working with cheaper
DBMS's. After a quick look on the market, PostgreSQL was the only one really
worth looking into.
But people liked MySQL, and I had to look for benchmarks. I found only one
(attached).
Not satisfied, I got PostgreSQL and MySQL
> Comparing PostgreSQL to MySQL is like comparing an 18-wheel Kenworth to
> a Porsche. The two are not equivalent
That's it. Major differences in features makes any benchmarking `apples to
oranges.'
> ... if you want a simple, very
> very fast READ-ONLY database, use MySQL.
BTW, can it be
Daniel Kalchev <[EMAIL PROTECTED]> writes:
> [ EXCEPT behaves oddly in the presence of NULLs ]
Yup, it does, because it's implemented like NOT IN, and NOT IN on a
set containing nulls can never return 'true', only 'false' or 'unknown'.
For example,
1 NOT IN (1,2,NULL)
is clearly F
Frankyl, Clayton:
Comparing PostgreSQL to MySQL is like comparing an 18-wheel Kenworth
to a Porsche. The two are not equivalent ... if you want a simple, very
very fast READ-ONLY database, use MySQL. If you want a full-featured
transaction-environment database for a huge, complex set of
Sandis Jerics <[EMAIL PROTECTED]> writes:
> As result, now all queries, written inside the php code on multiply lines,
> returns the following:
> ERROR: parser: parse error at or near " "
At a guess, you're having trouble with newline representations
(Unix convention is \n only, DOS/Windows conv
Subject:[SQL] renaming columns... danger?
> I just discovered that doing an alter table ... alter
> column (to rename a column) does not do a complete
> rename throughout the database.
> shouldn't rename update any index and key definitions?
> I'm very frightened right now, beca
