Page 1 of 1
Table Splitting, what does this actually do?
Posted: Sun 24 Feb 2019 23:18
by RobertK
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?
Re: Table Splitting, what does this actually do?
Posted: Sun 24 Feb 2019 23:19
by RobertK
What would it do if there are existing data in the current table?
Re: Table Splitting, what does this actually do?
Posted: Tue 26 Feb 2019 14:42
by Shalex
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?
Posted: Sat 09 Mar 2019 13:39
by RobertK
Shalex wrote: ↑Tue 26 Feb 2019 14:42
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.
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?
Posted: Wed 13 Mar 2019 14:55
by Shalex
RobertK wrote:how does the generated code know its a single table or multiple table?
Runtime knows this basing on the mapping generated by Entity Developer.