Actually I've had some case issues.

My PostGreSQL fields match python variables - just enclode the
fieldname in double quotes and it preserves the case

SELECT "callType" from "Calls" WHERE "costOfCall" > 10.00

Also my windows MySQL is not case sensative, and made all the
tables lower case, but my Unix version is.

So in testing I wrote CREATE TABLE Products(

and it created a table names "products"

My SQL was
SELECT * from Products
that did not work in windows, so I changed it to
SELECT * from products
which worked on windows, but not Unix.

MiddleKit type mapping or at least a central module is the way to
go, so at least the variables are all in one place.

-Aaron


> SQL may not be case-sensitive, but all SQL databases I've used
(Access, MS
> SQL Server, MySQL) are in fact case-preserving.  So you can
name your tables
> and columns FooBar and use them in your code as FooBar, and
they will show up
> in the SQL tools as FooBar.
>
> Sort of like the Windows filesystem, or Visual Basic code.
>




_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to