How to create better OO code in a relational database driven application where the database is poorly designed
I am writing a Java web application that consists mainly of a bunch of similar pages in which every page has several tables and a filter that applies to those tables. The data on these tables comes from an SQL database.
How to create better OO code in a relational database driven application where the database is poorly designed
I am writing a Java web application that consists mainly of a bunch of similar pages in which every page has several tables and a filter that applies to those tables. The data on these tables comes from an SQL database.
How to create better OO code in a relational database driven application where the database is poorly designed
I am writing a Java web application that consists mainly of a bunch of similar pages in which every page has several tables and a filter that applies to those tables. The data on these tables comes from an SQL database.
How to create better OO code in a relational database driven application where the database is poorly designed
I am writing a Java web application that consists mainly of a bunch of similar pages in which every page has several tables and a filter that applies to those tables. The data on these tables comes from an SQL database.
How to create better OO code in a relational database driven application where the database is poorly designed
I am writing a Java web application that consists mainly of a bunch of similar pages in which every page has several tables and a filter that applies to those tables. The data on these tables comes from an SQL database.
Where to put entity model classes in case of using a dataservice layer?
If my solution has both a “dataservice” project and a “business logic” project, where do the entity models, which represent database tables, belong?
Code design: is this specific case of monkeypatching in python acceptable?
I’m using python to do some research tasks. I have a class hierarchy for “tools”, where each object is an instance of a particular tool. They all share some functionality and have many similarities in their states.
Code design: is this specific case of monkeypatching in python acceptable?
I’m using python to do some research tasks. I have a class hierarchy for “tools”, where each object is an instance of a particular tool. They all share some functionality and have many similarities in their states.
Code design: is this specific case of monkeypatching in python acceptable?
I’m using python to do some research tasks. I have a class hierarchy for “tools”, where each object is an instance of a particular tool. They all share some functionality and have many similarities in their states.
Code design: is this specific case of monkeypatching in python acceptable?
I’m using python to do some research tasks. I have a class hierarchy for “tools”, where each object is an instance of a particular tool. They all share some functionality and have many similarities in their states.