On Apr 18, 2011, at 1:30 PM, Kent wrote: > For relations that aren't fully normalized, you occasionally need > uselist=False to specify one to one relationships (and maybe other > reasons). > > Currently these issue warnings like "Multiple rows returned with > uselist=False for lazily-loaded attribute...". > > Would you be in favor of a setting which would raise an exception > instead of a warning? > > I'm not happy about these database relationships in the first place, > so if the data is corrupt, I don't want to silently ignore the > problem, I really want an exception raised. > > What are your thoughts?
any warning can be made into an exception by raising the warnings filter: http://docs.python.org/library/warnings.html#the-warnings-filter for a new app its a good idea to just turn on all warnings as errors across the board. > Kent > > -- > 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 > sqlalchemy+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sqlalchemy?hl=en. > -- 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 sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
