How many images can be uploaded in the list-field?

Can you please tell me how many images can be uploaded in the list-field ?
How to limit their number to the user?

If you’re asking how many items can exist on a datatype’s list field, the answer is up to 10,000

However, in most cases it’s not recommended to have more than 100 or so (and often way less than that), but it all rather depends on the specifics of your app what you’re doing…

To answer your second question, you can limit how many things a user can create or upload by using conditions on you page elements and/or workflows, based on how many things the user has already created or uploaded…

If it’s image or a text-menu, 50 things.

Is that a question?…

Yes !

Sorry… I don’t understand the question?!… (what are you asking?)

Sorry for the translation.
If one current database row contains:
one cell 50 image-things;
second cell 50 text-things

This will work fine.
If the base is large?

It really depends on how and where exactly you’ll be loading that data…

It might be completely fine… it might be terrible…

It really just depends (and without knowing what you’re doing I can’t possible say)…

It’s quite a lot of data to have on a single thing, but again, it depends how you’re loading and using it as to whether it will cause any issues…

Maybe give some more context as to what exactly you’re trying to do…

I wanted to choose the right model.
There is a creator;
is - a thing;
There are many photos of this item.
It’s all there - the current cell. The creator has many such cells at different times.
There are also a lot of creators.

  1. You can store photos of things in another database and, using sorting by creator, pull them up to the first database.

  2. You can store photos of things in a datatype’s list field. Then one database is used.
    What would be the best way to organize the build?

Sorry for my English.

Again, it really depends on many factors which, without knowing more details about your app, I can’t comment on specifically…

But, from what you’ve described so far, option 1 is probably the best approach.

Then in the second base there will be a lot of things from different creators mixed up. Is it really the best choice for machine operation?

Is it really the best choice for machine operation?

If I understand what you’re asking then, from the limited info you’ve provided, almost certainly yes… but again, it depends…

To re-iterate my previous posts… what will work best for your app really depends on the details of your app…

I recommend spending some time learning about optimal database structures for performance and then you should be able to figure out for yourself the best approach to take in your specific use case…

This is a great book: The Ultimate Guide To Bubble Performance | Buy The Book (amliesolutions.com)

… but there is also plenty of useful info here in the forum, as well as the Bubble manual itself…

Thank you for your time and for my English.

Sorry for my English.