You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The project orderNumber string is limited to 20 characters. Sometimes costumers have complicated ways to create their numbers and we have hit the limit several times.
Describe the solution you'd like
Can we extend the limit to some generic value e.g. 256?
I think I could try to do that with some guidance.
Describe alternatives you've considered
We have also purchased the MetaFieldsBundle and could create a custom field. However, I think our proposal could save some trouble in the future.
The text was updated successfully, but these errors were encountered:
So, order "numbers", which made problems, had strings with a structure like 1234567890/WXYZ/SUBPROJECT/EMPLOYEE.
To allow this, one would need at least 50 characters.
I am not saying no, but blindly increasing every field to 255 chars is just not the right way to go.
For large queries increased field sizes might put more load on the entire system. There is a reason why you can limit the field size in databases, right?
If you can live with 50 characters, I am fine with increasing the field accordingly.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. If you use Kimai on a daily basis, please consider donating to support further development of Kimai.
Is your feature request related to a problem? Please describe.
The project orderNumber string is limited to 20 characters. Sometimes costumers have complicated ways to create their numbers and we have hit the limit several times.
Describe the solution you'd like
Can we extend the limit to some generic value e.g. 256?
I think I could try to do that with some guidance.
As far as I understand it would mean to:
Describe alternatives you've considered
We have also purchased the MetaFieldsBundle and could create a custom field. However, I think our proposal could save some trouble in the future.
The text was updated successfully, but these errors were encountered: