It's been a very busy year so far - I was on a death march project at work since December and I also became a father in March - but I've quit my job now so I'm finally getting around to doing this service layer refactoring.
As part of this refactoring I am also going to implement strict value checking on all data before they are persisted in the DB. In order to do value checking I need to know what the valid values for the properties of all entities should be. I'm starting with the simplest entity, Sport, so I need to know what the allowable values for the properties of a sport are. These are the validation rules I am currently assuming: * description: String, required (default ""), must be unique * met: Float, optional * weight: Float, required (default 0) * max_pace: Int, optional As mentioned earlier, in order to make this change feasible I will create a data migration script which will replace all invalid values with the defaults. - Nathan ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
