Open bartread opened 8 years ago
Another, possibly more flexible, approach, would be to support multiple [ForeignKeyReference]
attributes and/or a params [] of types in the constructor.
This is going to be aggro, and isn't super-urgent. Think I'm going to park it for now.
This would mean that if you had a common subset of properties that you often need to access in your DAO, without the rest of the row data from the database, you could do so by using the base class as, but the foreign key relationship would still work when you use a subclass containing properties for all the columns.