Let's say I'm building a database for vets and animals they care for. I have following entities:
class Animal : TableServiceEntity
class Dog : Animal
class Cat : Animal
Dog and Cat each has unique properties. And I have a Azure Table called Vets with vet.Guid as partition key and "Dog_" + dog.Guid or "Cat_" + cat.Guid as row key. If I were to retrieve everything by using AsTableServiceQuery() can I then cast an animal entity to Dog or Cat with those unique properties intact?
In broader sense, what's everyone's take on the trade offs in these kinds of situations? Between keeping Dog and Cat in one table for efficient querying but extra step in business layer and have separate tables with extra query but less messy code?