On Tue, Jun 5, 2012 at 8:47 AM, Sahananda (Jon) Wolfers <[email protected]> wrote:
> my understanding of SQL (and that may be wrong or limited to certain > versions) is that case sensitivity is a matter of how your database (or > perhaps even table) is set up. I looked into this a little bit. With SQLite column names are always case insensitive. It is impossible to have a table with one column fName and another column with FnamE. This is also true in MySQL. In MySQL, table names are case sensitive if the database is on a unix-like system, because table names are directly tied to a file. But, column names are always case insensitive. > On the other hand, ooRexx directory indexes are case sensitive when quoted, > so assuming your recordset gets the column names back from the db they will > be upper or lower or mixed case (I think that exhausts the possibilities), > and if you want to retrieve that index from the recordset then you need to > know whether the field is named 'lastname' or 'LASTNAME' or 'lastName'. If > you force the names into upper or lower case then your user does not need to > remember this, Not sure if you missed my statement on this. For a directory object, from the native implementation code, I always use an all upper case index. This allows, from Rexx code either: record~fName or record['FNAME'] and easy to remember for the Rexx programmer using either ooDialog or ooSQLite. You could not of course use: record['fName'] -- Mark Miesfeld ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
