FYI, did you know there is a 50 Active Object Entity limit per addon?

[Andy Brook [Plugin People]]

I just found out, AO-488. Just posting this for angst sharing.

I dont recall ever hearing about this limit being present, it would have made me more concious of trying to achieve 'nice' table hierarchies rather than just throwing XML in there. Fallbacks are generally unpleasant involving XML - I thought that was what AO was supposed to address!

Anyone else using AO heavily should bear this 'wall' in mind with their development...

Also, owing to the JIRA 6.1 reverse entity issue a developer will potentially have to allocate one entity purely for mapping purposes over and above their existing schema. If you have a lot of referrals, you need just as many mapping tables :(

[Adrien Ragot 2 · Accepted solution]

Thank you for sharing this useful warning. +1 for the karma ;)

[Andy Brook [Plugin People]]

Jason, thanks for the link, the code doesnt shed much light onto the reasoning, though :/

[Andy Brook [another me]]

darnit, too many me's.

[Andy Brook [another me]]

Just applying database normalisation to an ever growing data model, table count is proportional to complexity :/ Hmm, 50 seems a bit of an arbitrary number though...

[jhinch (Atlassian)]

I'm very surprised (and impressed) that you need 50+ tables for your plugin. The poorly named NamesLengthAndOracleReservedWordsEntitiesValidator seems to be where this is coming from.