Yet another possibility with its own set of problems would be to include a developerId column in every table and query: you could then give each developer their own copy of data within the same db.
david jencks On 2002.01.10 03:09:43 -0500 Jim Cheesman wrote: > At 05:52 PM 09/01/02, Phil wrote: > > > > What if multiple developers run the test at the same time on the same > > > database table? > > > >Shouldn't Sybase have table/row locking? > > > Doesn't help - suppose the following (developers A and B): > A: Writes test data to db > A: Runs test to modify data > B: Writes test data to db > A: Checks test data in db > &c. > > The db rows/tables are not necessarily locked in between the steps > outlined > above. > > > One (very messy) solution would be to install MySQL or similar to test > against, and run main tests on a seperate build machine using Sybase. Of > course, you're not testing the database itself, but rather the jdbc/code. > > The only other solution that seems to present itself is the one suggested > > by Steve Loughram in another message: some kind of locking mechanism to > prevent two developers running their tests simultaneously. > > > > Out of interest, why are the developers running seperate tests? Is it not > > possible to integrate these tests and run them from a separate machine > at, > say, lunchtime and before/after work? > > > Jim > > > -- > > * Jim Cheesman * > Trabajo: > [EMAIL PROTECTED] - (34)(91) 724 9200 x 2360 > If a pig loses its > voice is it disgruntled? > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
