Dirk Meyer wrote:
Rob Shortt wrote:
BTW I'm still using sqlite 1.
Strange result['foo'] should be identical to result.foo in
sqlite1. Looking at my code, you just broke sqlite2 support. :(
I guess I could change the code so that result['foo'] also works with
sqlite2. But this will slow down things. Sqlite2 is much faster
because it only returns the result as list. So you can only access
result[0], result[1], etc. This is fast, but not very nice to
read. Creating an object to support result[key] and result.key will
slow things down (like sqlite1).
I will try to fix it. The _best_ way to only use result[int].
Later I can install sqlite 1 and run a test here. I have no problem
with requiring sqlite 2 if it's just as available to users.
-Rob
--
-------------------------------------------------------
Rob Shortt | http://tvcentric.com | Freevo
[EMAIL PROTECTED] | http://freevo.sf.net | Free your TV
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Freevo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freevo-devel
