On Apr 24, 2004, at 11:17, Jan Wieck wrote:
I don't think that we will break backward compatibility for existing
PostgreSQL specific code in order to gain CamelCase+MySQL porting ease
by adopting an even less standard compliant behaviour than we
currently have.
I understand and agree that breaki
On Apr 24, 2004, at 00:48, Tom Lane wrote:
You do realize that any such patch would be at least a thousand times
larger than that?
I am coming from a state of ignorance past the fact that commenting out
four lines of code appeared to create the behaviour I desired. I knew
that just changing it to
Hi EMF,
emf wrote:
Hello, postgresql hackers.
All of this breaks when I start to use postgresql, because all of the
attributes become lowercased.
Well, I'm afraid that something will have to change in the app. Your
email arrives while we are in the middle of a small war around the
subject of c
Hello, postgresql hackers.
I am working with a client with a 20k record MySQL database (that will
shortly expand to 100k/1m) and a few thousand lines of PHP code that
does a lot of DB interaction.
Their application, with a lot of relationships between data and a bunch
of data integrity require
