Mister, > Question: will there be a :signed => true/false property?
Specifying a :min equal to or greater than 0 will result in the Numeric property becoming unsigned in DB's that support it. We can also use :min and :max together to choose the most efficient column type that can store the allowable range, and set up automatic validations if dm-validations is being used. The :min and :max option communicate more about our intentions than :signed, and since we can infer this from the :min it would be redundant to add a second way of specifying the same constraint. > Also, who do we work with to ensure nothing is overlooked, or assumed > unimportant? I would be the person to speak with. I'm often in #datamapper or #dm- hacking on irc.freenode.net under the nickname "dkubb". You can also bring things up on the mailing list too. Either way is fine with me. The best way to communicate importance is through working code. Sending me a pull request with the actual well written, specced and documented code is by far the best way to ensure something makes it into dm-core 1.0. However it's best to speak with me first and find out if there were any plans around how a specific feature will be added, and where, just to ensure your time is spent wisely. -- Dan (dkubb) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
