Marc G. Fournier wrote:
On Tue, 6 Jul 2004, Andreas Pflug wrote:
An external tool helping translating sql is fine, but nothing to be defined todo for core pgsql IMHO. I still believe some minor "oracle helper" behaviour (not to call it oracle compatibility, to avoid wrong expectations) should be added. Currently, pgsql appears a bit arrogant towards those oracle centric people (always a matter of point of view, of course). We could avoid this by offering some concessions.
Actually, we had added awhile back a set of 'Oracle compability' stuff to the backend, to handle some of the non-standard functions that Oracle users had access to ... is there a reason why that can't be extended? Or are we talking about *really* core changes here?
I don't think so. I'd like to say "we're support oracle style syntax as far as it's reasonable in the context of pgsql, and we're supplying best practice advice for some more stuff".
Regards, Andreas
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
