Agreed - it makes more sense to have a generic enum type which may fall back
to software should the db not actually support it. Having said that, in
terms of using (selecting/updating) an enum field the syntax should be quite
similar across implementations. While I'm not familiar with databases
, Michael Bayer mike...@zzzcomputing.comwrote:
On May 27, 2009, at 12:09 PM, Dimmich Damian wrote:
Would it, based on the above assumption, not be possible to have a
generic enum type that figures out what to do based on what type of
database we are connected to without needing to specify MSEnum
