business-logic

I have a class : Schedule. public class Schedule { private int locationNum; private int cost; private String costReason; private Date weekOfChange; private Date dayOfChange; private String changeReason; // and all those getters and setters public Schedule(int locationNum, int cost, String costReason, Date weekOfChange, Date dayOfChange, String changeReason) throws ApplicationException { //change is all or nothing - all attributes are present or none if((weekOfChange!=null && dayOfChange!=null && changeReason!=null) || (weekOfChange==null && dayOfChange == null && changeReason == null)) { this

With Data Annotations it's now easy to localize error messages using Resource.resx files like this for example: public class Student { . . . [Required(ErrorMessageResourceName ="Required", ErrorMessageResourceType = typeof(StudentResources))] [StringLength(16)] [Display(Name = "FirstName", ResourceType = typeof(StudentResources))] public string FirstName { get; set; } . . . } Now, let's say I want to check if a Student has already made a Payment for a given month and year: public bool CheckIfAlreadyPaid(Payment payment) { return repository.GetPayments().Any(p => p.StudentId == payment

I wonder, is it bad or good idea to use auto increment primary key as business entity identifier such as Partner Id or Account Number ? Also, what pitfalls I can face if I'll choose that approach? I don't think everyone shares the same opinion, but I do think it is bad practice. Passing ID's to the user as the 'key' is bad in my opinion, for a number of reasons: ID's aren't natural to users. They are not talking about project '1474623', they are talking about project 'ABC'. They aren't talking about person '363528', they are talking about 'Patrick Hofman'; ID's are fragile. You can't really

Following the concept of CQRS (Command Query Responsibility Segregation), I am directly referring the DAL in my MVC application and doing all reads via the ViewModels. However a colleague of mine is asking me what will you do when any business logic has to be applied when doing a read. For e.g. if you need to compute a percentage value in scenario like below: //Employee domain object class Employee { string EmpName; Single Wages; } //Constant declared in some utility class. This could be stored in DB also. const Single Tax = 15; //View Model for the Employee Screen class EmployeeViewModel {

Here is the code I currently have that gives me the last 12 days SELECT * FROM table WHERE analysis_date >= current_date - interval '12' day; analysis_date is the date column in the table. I understand why this isn't working because it's not accounting for business days. How can I rewrite this so that I get an interval of the last 12 business days? I tried search online and found extract(dow from (date)) But I couldn't find an example where I need a weekday interval. Any help would be appreciated. This can be solved with a CTE: WITH business_days_back AS ( WITH RECURSIVE bd(back_day, go_back)