> I used arrays way back when I first started using Postgres but gave > them up pretty quick. I found that whenever I used an array, a small > table was a lot simpler and more flexible.
That would be a *lot* of tables for me, and I doubt that would be acceptable. I wanted this app to scale well, and having thousands of tables lying around would make a nightmare on the sysadmin side. Besides which, I'm returning JSON from the server, so there's no reason for me to have to format things myself when they can be returned that way from the DB. On top of that, I allow variable-length arrays--a table would have to be static, or ALTERed each time I needed more space--and that would increase the size of the table not by one cell, but by however many rows I had at that point, even if that entry was the only one to use the last column(s). I may have to switch to psycopg, but thanks for the help and ideas, guys. If you do fix the arrays, let me know and maybe I can switch back, but at the moment I don't have the patience to fix the library myself. Cheers! -- Mark Holmquist Student, Computer Science University of Redlands [email protected] _______________________________________________ PyGreSQL mailing list [email protected] http://mailman.vex.net/mailman/listinfo/pygresql
