I have a Catalyst based application with a DBIx::Class model on top of an SQL database persistence layer. Following ‘best practice’ all my business logic is all within the framework and not within the database.
One particular requirement is that the date of an event is between the start date and end date of a parent object. I have a series of tests and am satisfied in my development environment this is always the case. However, in the live environment there are a number of records in the database that do not satisfy this requirement. I have realised that this is due to the high state of flux of all date values and that some users are amending the dates of the parent entities at the same time as others are creating the associated events.
I have two questions:
In reply to Catalyst Concurrency Control by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |