Can there be any restrictions appear in Core Data? e.g the number of max rows could be inside a table/Entity? Just how much data can live in the DB?

Generally if some document can describe all type of restrictions available within the Core Data (for iOS)?

Update: w.r.t answer distributed by @TechZen, my question was implied that I/Core Data is going to be using sqlite in the after sales. But to simply obvious the purpose, I'm meant to use sqlite so when I'm speaking about restrictions of Core Data, I'm not directly asking limit of sqlite (database store).

Same with there any restrictions enforced by core data apart from the limitations from the sqlite if we are speaking about iOS atmosphere?

You will find no logical limitation on Core Data itself beyond individuals enforced by situational memory, disk space etc. However, if you are using an SQLite store, you receive the default limitations of SQLite itself. If you're writing for iOS, you won't ever hit individuals limits.

The only real practical limitation you hit with Core Data originates from memory issues triggered by reading in large blobs e.g. attempting to store images or audio within an SQLite store. That may be prevented by storing the blobs in exterior files.

Being an aside, I'd warn you will be able to tell incidentally you phrased the question, that you are looking at Core Data wrong.

Core Information is no object wrapper for SQL. Core Information is not SQL. Organizations aren't tables. Objects aren't rows. Posts aren't characteristics. Core Information is an item graph management system that might persist the item graph and might use SQL far behind the curtain to do this. Attempting to think about Core Data in SQL terms will lead you to completely get me wrong Core Data and lead to much grief and wasted time.