Re: DB_DataObject, part 2
| From: | Justin Patrin | Date: | Fri, 22 Sep 2006 04:27:34 +0000 |
| Subject: | Re: DB_DataObject, part 2 | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-25204@lists.php.net to get a copy of this message | ||
On 9/21/06, Chris Boget <chris.boget@wild.net> wrote:
Hold on....MDB2 and DB_PORTABILITY_NONE? If you're using MDB2 as your backend you should be looking at the MDB2 docs. -- Justin PatrinDB docs? Silly me. :( I found it and I found the portability option that forces the fieldnames to be lowercase: DB_PORTABILITY_LOWERCASE. However, changing that option does not appear to be doing anything. Here are my options: $options: Array (Where in the documentation could I read about this? I don't see it on the first 3 pages (DB_DataObject, Introduction, Configuration Options) of the dataobject docs...[database] => 'this' [schema_location] => 'that' [class_location] => 'other' [require_prefix] => DataObjects/ [class_prefix] => [debug] => 3 [portability] => 0 [db_driver] => MDB2) portability 0 is DB_PORTABILITY_NONE. That *should* override the lowercase portability option, I would think. But I'm still getting those 4 extra lowercase columns. In fact, I don't see anywhere in DB_DataObject (or MDB2 for that matter) that even checks that portability option. Am I missing something? I must be.