> 2) why in the world was case sensitivity introduced at all? AFAIK, the SQL > standard explicitly states that names are case insensitive, and it seems to me > that PG goes against that standard. It doesn't. It simply folds to lower case rather than upper case. If things are truly ...
had to compile yourself, wasn't available on many shared hosts (still is case, but the story is getting better), and it had some pretty annoying user-friendly problems (it still does to some extent which we shall go into later, but is much better than when...
That was a log from the legacy driver (2.5) I tried just in case. I also tried Unicode (beta) with same "success". But hereis the part of the log from the ODBC3.0 psqlodbc.dll driver (it has slightly different diagnostics): ... [-787737]READING ATTTYPMOD [-787737]CI_read_fields...
Such is the case with geocoding and thePostGIS tiger geocoderspecifically. Lots of interest has revived on that with people submitting bug reports and we've got paying clients in need of a fairly easy and speedy drop-in geocoder that can be molded to handle such things as road way locations...
if this *does* turn out to be the case, does it make sense to have the script check perms up through the physical/path of the cwd and report with a more specific/desciptive error if they're not at least 555 on the mount point?