Corey Donohoe wrote:
I currently have to support both postgres and oracle for work. I'd
like to use booleans but I ran into a wall when I found oracle didn't
support them. The fix was really small and I adopted the convention
of NUMERIC(1) being boolean. It also uses a similar approach as the
mysql driver by allowing it to be disabled if the app doesn't want to
leverage booleans.
I bounced the idea off of Michael Schoen but he thinks people might be
using NUMERIC(1) for values between 0-9. I can see his point but I
think for most the most part people would want to have this option
available for consistencies sake.
I agree. We use NUMERIC(1) for booleans here also and having the ability to
decide how to map it would be appreciated.
Blair
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
