Hi Dan, > None that I can think of. If you create ticket for this, and submit a > patch I will make sure it gets in before the next RC (which at the > earlier will be tomorrow night, and the latest Sunday night).
As I remember there was a talk about date/time properties and their precisions some time ago (could be a year ago). I remember that someone had following argument against more precision: if you set updated_at to 2009/06/26 12:25:00.123456 and DB will store milliseconds as .1234 (because that's its precision) this would mean that we have different data in DB and in model. Probably this could make tracking dirty attributes more tricky. But I think we can come up with some solution to this, ie cast time to the precision which DB uses upon attribute assignment. What do you think? Does property have access to such information like underlying datetime/timestamp/whatever column's precision? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
