unfortunately. yes. i think as long as the data don't collide, it should be safe.
so i make sure every name and email address are unique when i create them. having said that, i still rather see transactional support working correctly. On Nov 26, 3:09 am, Ashley Moran <[email protected]> wrote: > On Nov 25, 2009, at 10:47 pm, trung wrote: > > > I gave up on transactional fixtures. Instead, I make sure everytime I > > create a model using dm-sweatshop, it always passes in a unique email > > address or username for example so it won't violate the unique > > constraint. Seems to be working okay. > > Does that mean you have data from one spec example still in the database for > the next? > > --http://www.patchspace.co.uk/http://www.linkedin.com/in/ashleymoran -- 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.
