Hello,
I'm trying to add a lot of fields to the Incident class, but I got mysql error saying that the row size was too large.
So, I want to know if creating more tables will solve this problem? and is there any doc explain about creating table and saving data into 2 tables?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just curious - how many fields are you trying to add, and what kind of attributes? Lots of AttributeBlob or AttributeText fields or something, or case logs?
Not sure if an extra table (join) will help you or if you'll run into the same (MySQL) limitation.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
linked classes? something like creating another class under Incident, right? If yes, I'm trying to do it but still find the way to show the fields in the Incident page.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I'm trying to add a lot of fields to the Incident class, but I got mysql error saying that the row size was too large.
So, I want to know if creating more tables will solve this problem? and is there any doc explain about creating table and saving data into 2 tables?
Just curious - how many fields are you trying to add, and what kind of attributes? Lots of AttributeBlob or AttributeText fields or something, or case logs?
Not sure if an extra table (join) will help you or if you'll run into the same (MySQL) limitation.
I'm trying to add like 115 fields including
77 AttributeString
15 AttributeDateTime
17 AttributeEnum
6 AttributeEnumSet
115 fields?!
What kind of info are you all trying to add here to this one object?
This will make your environment quite slow in the end...
There's no way to optimize your data model? E.g. use typology instead of strings? Work with linked classes?
Hi, Jeffrey
Do you have any advice? How many fields should not be added so as not to affect performance?
Depends a lot on your infrastructure as well, so there's no straight-forward answer.
Use common sense to see if it's a value that's being re-used; and if you implement it as some sort of "typology" or enum value perhaps.
linked classes? something like creating another class under Incident, right? If yes, I'm trying to do it but still find the way to show the fields in the Incident page.
Take a look at the "AttributeExternalField" info (works in combination with AttributeExternalKey)
I'm gonna try it. Thank you so much Jeffrey!