Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Database uses VARCHAR(255) for String columns #667

Open
andrewazores opened this issue Sep 24, 2024 · 0 comments
Open

[Bug] Database uses VARCHAR(255) for String columns #667

andrewazores opened this issue Sep 24, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@andrewazores
Copy link
Member

Current Behavior

ex.

The database definition sets up the tables so that various String columns (active recording names, automated rule names and descriptions) are of varchar(255) type.

Expected Behavior

All of these cases should be audited and either the string length limit removed by using some Large Object type, or else the application should do length validations when requests to create resources are processed so that better error messages can be reported to the client.

Steps To Reproduce

No response

Environment

No response

Anything else?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Backlog
Development

No branches or pull requests

1 participant