When you use table splitting,
1) Entity developer creates additional new classes for a single table?
2) Entity developer create additional new classes and additional new tables? (just like creating a table with a foreign key?)
It seems to do #2, creates a new class and a new table?
Table Splitting, what does this actually do?
Table Splitting, what does this actually do?
Last edited by RobertK on Sun 24 Feb 2019 23:20, edited 1 time in total.
Re: Table Splitting, what does this actually do?
What would it do if there are existing data in the current table?
Re: Table Splitting, what does this actually do?
After table splitting, Entity Developer works with a single table. If you do Regenerate Storage, the number of tables becomes equal to the number of classes.
Re: Table Splitting, what does this actually do?
What you are saying here is, if you split it without regenerating storage, then ED will deal with a single table but if you regenerate storage then there be 1 class per table. But how does the generated code know its a single table or multiple table?
Re: Table Splitting, what does this actually do?
Runtime knows this basing on the mapping generated by Entity Developer.RobertK wrote:how does the generated code know its a single table or multiple table?