This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi there,
Sorry for what might be an obvious answer but what does it mean when the Express and Standard versions have an 8 model class limit and a 30 model class limit respectively?
Does this mean that using the standard version, only 30 classes mapped to 30 tables in the backend DB can be generated? Does a runtime exception occur when 30 is exceeded or a compile time error?
Or are the Lightspeed Model classes the items you add to a project but can contain any number of table mapping classes?
Thanks.
|
|
|
The limit refers to how many classes can be mapped to the backend database, and is enforced by a runtime exception. For example, if you are using Express edition, when LightSpeed encounters the 9th class that needs to be mapped to a table, it will throw an exception. Similarly if you are using Standard edition and LightSpeed encounters the 31st class. Therefore, you can add any number of entity classes to a project, but you can only *use* as many of them as the edition supports. I'm not sure I've quite understood your final question, but the limit refers to *classes*, not to files or models. Thus, if you have a .cs file which defines 9 entity classes, or a graphical model that defines 9 entities, that would cause an exception in Express edition (again, at runtime, not compile time). Does that answer your question? If not please do follow up. |
|
|
Yes, thank you.
My final question was in regards to my misunderstanding between model class and .lsmodels that you can add to a project. I was unsure if the limitation was on the number of .lsmodels you could add to project but you've answered it in the first part.
|
|