Domain entity with 1450 columns

0
Hi team – we have a requirement where data from another application will be downloaded and uploaded into Mendix application for data sanity rules, approval and posting to data lake either on demand or as scheduled event.   Can you pls. advise how can we have a table with 1450 columns? Shall it one table or any vertical partitioning needs to be applied?   Thanks, Deepak
asked
1 answers
3

Hi Deepak, 

this heavily depends on the meaning of your data. If all 1450 columns are necessary everytime you get a respective object, then the answer is “No”. But if there is only a partial set of columns needed, and the rest can be fetched when needed, then you should split it up. 

Best have a look at https://docs.mendix.com/howto/general/community-best-practices-for-app-performance 

Here are some do’s and don’t summarized, which should help you with your decision

answered