Tag Info

New answers tagged

1

It depends on whether or not you need to do anything "interesting" with that additional, client-specific data. In practice, it is unlikely that any processing will take place on custom fields, since you would have to provide that processing yourself, with some sort of plugin infrastructure or provide custom builds for each client, an arrangement which can ...


-2

In my honest opinion having different sets of tables for different sets of users will add complexity to your code by having 'X' amount of SQL queries. Because for one schema you'll have one SQL Query string for grabbing the data from there, but for another schema you'll have another SQL Query string from grabbing data from there. Plus I think it makes it ...


0

This sounds like a good opportunity to use the Strategy design pattern. You will have a data access strategy that will check the environment and execute the proper code depending on what the back end is. "Checking the environment" could be something as simple as using an environment variable or something more high level like injecting the appropriate query ...


5

This is essentially what an Object/Relational Mapping Framework (such as Hibernate) can do for you. It provides a layer on top of the database that abstracts away the details of querying the database by providing a database-independent layer and query language. Hibernate provides (among other ways of querying the database) HQL for this: from Cat as cat left ...


0

This sounds like a very tough nut to crack, I'm not even sure it can be cracked at all. The database is going to become enormous and hence slow in a short period of time, caching is not going to happen on any appreciable level. Keeping multiple copies of such big files for versioning is going to require an inordinate amount of disk space (which is cheap, ...



Top 50 recent answers are included