> Of course, the point of using an ORM in the first place is to specify > the constraints on the model, not on the underlying DMBS. This is the > same argument as why you'd rather use a DBMS instead of writing the > physical storage layer yourself.
especially if we come up now how to support the different ways to ensure constraints on the different databse systems, or even database formats. ;) > BUT this doesn't mean that the ORM is not allowed to propagate > constraints from the model into the DBMS if it would help avoiding to > DOUBLE ( o_O ) the numer of database roundtrips in the common case. As > Thomas already noted, there *ARE* ways to implement this AND be race-free. > > Which only goes to show that glitz and time to market always trump > technical superiority. Just put it into vendor! where is vendor in puppet ;) cheers pete -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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/puppet-dev?hl=en.
