What kind of object relational mapping is appropriate here?
In my database I have a table that looks like this Master(ID, Name, Attr1…). Every ID will have at least 1 entry in additional tables that have additional attributes. Those tables specialize the master table.
What kind of object relational mapping is appropriate here?
In my database I have a table that looks like this Master(ID, Name, Attr1…). Every ID will have at least 1 entry in additional tables that have additional attributes. Those tables specialize the master table.
What kind of object relational mapping is appropriate here?
In my database I have a table that looks like this Master(ID, Name, Attr1…). Every ID will have at least 1 entry in additional tables that have additional attributes. Those tables specialize the master table.
What kind of object relational mapping is appropriate here?
In my database I have a table that looks like this Master(ID, Name, Attr1…). Every ID will have at least 1 entry in additional tables that have additional attributes. Those tables specialize the master table.
Finding next free IP in a network
I have an IP network and want to automatically find a free IP address to provision a new server. Due to frequent server additions/removals the used IPs might be quite fragmented over the whole address space. To effectively check if an IP is free I have to ping and ask the DNS system, which is considered expensive. So I want to minimise these lookups and store some information about used/free addresses in a relational database. This should give me good candidates and I only have to do a few such lookups.
Finding next free IP in a network
I have an IP network and want to automatically find a free IP address to provision a new server. Due to frequent server additions/removals the used IPs might be quite fragmented over the whole address space. To effectively check if an IP is free I have to ping and ask the DNS system, which is considered expensive. So I want to minimise these lookups and store some information about used/free addresses in a relational database. This should give me good candidates and I only have to do a few such lookups.
How does accumulating large amounts of business logic on the model objects make building strong service contracts harder?
I heard a couple of times that putting business logic in database models is bad down the road.
How does accumulating large amounts of business logic on the model objects make building strong service contracts harder?
I heard a couple of times that putting business logic in database models is bad down the road.
How does accumulating large amounts of business logic on the model objects make building strong service contracts harder?
I heard a couple of times that putting business logic in database models is bad down the road.
How does accumulating large amounts of business logic on the model objects make building strong service contracts harder?
I heard a couple of times that putting business logic in database models is bad down the road.