[Resolved] Using Toolset as a database – how many repeater elements are feasible?

[Author]

Posts

[andrewG-16]

I'm looking to use Toolset to manage a database of architectural finds. In a standard app we'd have several tables - a 'context' table which contains all the areas within the dig and the info about each area, then within each context you can have multiple photos, finds and some other things. So usually you'd have the context table with a one to many relationship to finds, photos and a few other things. Now, having seen repeater groups, I'm thinking I could just have a 'context' post type, then have repeater groups for finds and photos. My question is, how many records can be added within repeater groups before performance becomes an issue. If we had 50 finds and 50 photos, all within repeater groups within a single context, is that going to be too many?
Should I split these into separate post types and have relationships between them instead, thus modelling a more traditional database?

[Luo Yang]

Hello,

The Toolset repeatable field groups are based on one-to-many relationship, so there isn't any limitation for "how many records can be added within repeater groups", you can add as much as you can, it depends on your server capability.

So you don't need to split them into separate post types.

[andrewG-16]

Great - thanks for the advice. I’ll give it a go!