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.

Sign up for GitHub

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

Jump to bottom

Use QA_DB_MAX_CONTENT_LENGTH instead of fixed "8000" for content length #28

Open
q2apro opened this issue Jul 6, 2020 · 0 comments
Open

Use QA_DB_MAX_CONTENT_LENGTH instead of fixed "8000" for content length #28

q2apro opened this issue Jul 6, 2020 · 0 comments

Comments

@q2apro
Copy link

q2apro commented Jul 6, 2020

In file https://github.com/svivian/q2a-edit-history/blob/475cb1f9f007a3525c9ac6f0ee79e5cfd6644631/qa-edit-history.php use instead:

content varchar(8000) DEFAULT NULL,

this:

content varchar(".QA_DB_MAX_CONTENT_LENGTH.") DEFAULT NULL,

I just noticed that changes from my 12000 char content in ^posts table were not stored completely.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@q2apro