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

Longer field names please! (Problem porting from another database) [CORE1948] #2386

Closed
firebird-automations opened this issue Jun 21, 2008 · 5 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Tim Kelly (m00bh000)

Duplicates CORE749

Hi the maximum field length of 32 bytes is very restrictive and causes a lot of unneccessery work when porting applications from servers which support a longer maximum field length.

Would it be possible to support longer field-names?!! 128 should do.....

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Link: This issue duplicates CORE749 [ CORE749 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Duplicate [ 3 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: bluish (bluish)

This is a very strong limit that oblige us to difficult workaraounds.
Please raise the limit!

@firebird-automations
Copy link
Collaborator Author

Commented by: @asfernandes

It was increased to 63 characters in v4. See CORE749.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant