-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Fixing sql fields #13091
Fixing sql fields #13091
Conversation
Added missing PostgreSQL ALTER statement.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
need some small fix for postgresql the #__fields_groups
lacks 2 fields than mysql checked_out
checked_out_time
"access" bigint DEFAULT 0 NOT NULL, | ||
PRIMARY KEY ("id") | ||
); | ||
CREATE INDEX "#__fields_idx_checked_out" ON "#__fields_groups" ("checked_out"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sql CREATE INDEX "#__fields_idx_checked_out" ON "#__fields_groups" ("checked_out");
cannot see a checked_out
field on #__fields_group
table declaration
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems missed from mysql table declaration
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed missed those on the update files. Do you want to do the PR or should I do it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't better to revert+fix+remerge ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nah, we just can add those two columns in a different PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok see #13102
* MSSQL - update sql for Custom fields (#11833) MSSQL - update sql for Custom fields (#11833) * MSSQL - update sql for Custom fields (#11833) MSSQL - update sql for Custom fields (#11833) * MSSQL - install sql for Custom fields (#11833) MSSQL - install sql for Custom fields (#11833) * minor cs + defaul values * move hits field on a new line move hits field on a new line * removed version, hits fields removed (version, hits) fields #12674 * removed (version,hits) fields removed (version,hits) fields #12674 * mssql com_fields#13091 Fixing sql fields #13091 * mssql com_fields#13091 mssql com_fields#13091 * [com_fields] No need for an alias in fields groups. #13115 [com_fields] No need for an alias in fields groups. #13115 * [com_fields] No need for an alias in fields groups. #13115 [com_fields] No need for an alias in fields groups. #13115 * missed comma missed comma * missed comma missed comma * update for #13175 from extension to context * update for #13175 from extension to context * update for #13246 update for #13246 * updated for #13246 updated for #13246 * added the missed DEFAULT added the missed DEFAULT * added space before ( added space before ( * added space before ( added space before (
Pull Request for Issue #13088.
Summary of Changes
Testing Instructions
Documentation Changes Required
None
Notes
Once this is merged, fields still need SQL Azure SQL commands.