On Friday, July 11, 2014 4:31:54 PM UTC-7, Chris Fincher wrote: > > I looked again and realized that the dba_tab_cols errors not being caught > was our fault. We were overriding all of the db's execute_* methods > (cringe) and wrapping DatabaseErrors in another kind of error, so by the > time it got back to schema_parse_table, it wasn't a DatabaseError anymore > and wasn't getting caught. I got rid of the overrides, and it's now being > rescued properly. > > I'm still working on the #tables and the primary keys. I'll update if I > find something. Glad to hear that all_tab_cols is working well. >
OK. Note that as I mentioned, I just switched the #tables implementation to use all_tables, so make sure you test the master branch and not the last release for that. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
