On Wednesday 18 February 2004 12:38 pm, Ben Ramsey wrote: > I know that it may be somewhat irrelevant to solving the problem at hand > (and, in fact, I think your current method is probably the best method), > but I was just wondering why you needed to change the names of your keys > at all. Why is it not programmed so that the keys already have the > names you want them to have? >
In a nutshell 1. My problem is with current SQLite: http://marc.theaimsgroup.com/?l=php-db&m=107705406519266&w=2 2. I posted a question to the SQLite mailing list, and got these replies "Yes, this is the correct behavior, without the table 'prefix' if you have common column names in the result set the data would lost." AND "The old PHP interface did strchr() on the column names in order to 'strip' the any data (table name) before the column name. This is rather inefficient and should not be done and thus was removed." So to have my DB abstraction class stay compliant with other DBs, I have to modify the returned keys from an SQLite query... Life sucks, so I deal with it... :( -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
