Hi,
I'm sorry but it' still not a complete guideline.
My table is named Setting and has following columns:
SET_id, int: record's id; autoincrement
SET_key, nvarchar(64): record's name
SET_category, nchar(1): class discriminator: 'T' for texts (SET_value is the value), 'O' for options (SET_option is the value)
SET_value, nvarchar(256): value for texts
SET_option, nvarchar(64): value for options
The classes:
The config file:
When trying to access the database is that:
Class EX.Common.DAL.SettingOption must use vertical inheritance as
it has siblings and the base class does not have a descriminator (jdo_class) column
1. jdo_class or voa_class?
2. I've tried a lot of combinations:
- database column name changed to voa_class / jdo_class
- removing this column from both - config and class definition
Nothing helped. How this discriminator column should be declared?
On the other hand. It's a pity that there is no single source of definition of both: database and objects. They are partially defined in C# code - by persistent classes. But they are partially defined in app.config also - for example: the model of inheritance; and physical definition of columns, of course (length and scale). It would be wonderful to model the database and its objects in a single XML file and one shot: create the database; second shot: create classes....
And yet another thing: you have decided to declare attributes (in app.config) using <extension key=... value=.../> template. The major consequence that there is (and can't be) no prompt for "value". If you declared them as attributes (e.g. <class name="xx" inheritance="vertical" .... > instead of <class name="xx"> <extension key="inheritance" value="vertical" /> </class>) yould could define prompt in every case.
Uff. I'm sorry for so long reply / question / considerations :-)
Regards
Tomasz