I too have just been bitten by this. >From r2950 to current trunk, all fieldnames in queries have been .lower()d This breaks my code which uses the real fieldnames - things like maxExtent & maxResolution. This code all worked fine before on MySQL, PotsgreSQL & sqlite.
In the spirit of not breaking backward compatibility, the not lower()ing should be the default. If some cases want this lower()ing then they should be the ones who add an extra flag to get that behaviour, surely? F
