Forgot your password?

typodupeerror

Comment: Re:Pushing to look at alternatives, really? (Score 1) 137

by Sxooter (#37534426) Attached to: Oracle May 'Fork Itself' With MySQL Moves

QUOTE: The worst part was differences with dates and the pickyness of postgres with joins

Urgh. The ANSI standard very clearly states that if you mix implicit and explicit joins, the explicit joins go first. So, this query:

select * from a,b join c on (a.id=c.id)

won't work in any compliant database, because a.id doesn't exist yet when joining b to c. And guess what happened in MySQL v5.1? That type of join started throwing an error just like pgsql does.

Comment: Catch on? Like this? (Score 1) 128

by Sxooter (#37374640) Attached to: Type Safety Coming To DB Queries

select 1 where '2001-01-02 00:00:00'::text between '2001-01-01 00:00:00'::timestamp and '2001-01-05 00:00:00'::timestamp;
ERROR: operator does not exist: text >= timestamp without time zone
LINE 1: select 1 where '2001-01-02 00:00:00'::text between '2001-01...
                                                                                                        ^
HINT: No operator matches the given name and argument type(s). You might need to add explicit type casts.

Hey whadya know, postgres has been doing this for years now.

Comment: Re:And this opinion has nothing to do with the fac (Score 1) 509

by Sxooter (#36705386) Attached to: Facebook Trapped In MySQL a 'Fate Worse Than Death'

Stonebraker abandoned first Ingress as hopelessly broken to build Postgres. Which he then abandoned as hopeless broken to move on to various projects like the more recent VoltDB. He left Postgres a VERY long time ago, and hasn't been involved in the project since well before pg 7.0 hit the scene.

FLASH! Intelligence of mankind decreasing. Details at ... uh, when the little hand is on the ....

Working...