TerranceK4053 Member since 2018 45 posts
Posted: 11 months ago
Last activity: 11 months 2 weeks ago

Data types for multiple implementations

I have an application that supports multiple implementations of it with a particular concrete data class being used. Each implementation has approximately 30000 instances of this data class. Is it better to use just one table for all implementations and have a column in the table that indicates the implementation or create a separate table per implementation and thus a different data class per implementation? A different data class per implementation means to me having to support different code to access this table to a certain extent at least I would think to create instances though querying the instances could possibly be performed with a single report definition set to look at implementation.

***Edited by Moderator: Lochan to update platform capability tags***

Low-Code App Development Data Integration Reporting
Share this page LinkedIn