On Thursday 16 August 2007 00:33:57 [EMAIL PROTECTED] wrote: > > Reflection should be configurable whether to stop at dialect > > level (SLint) or go back to abstract types (types.Int) - see my > > autoload.py. > > why would one want to stop the reflection from going back to > abstract types? > i.e. if the current reflection (dialevt-level) is made to autoguess > the abstract SA type, would this break something?
Answering myself, dialects may have richer types that SA.abstract ones, in which case extra ones stay as is. Also, seems there are duplicates, because of which the abstract<->dialect is not 1:1, e.g. postgres has bigint and int that are both SA.integer. how about these? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
