-
Suggestion
-
Resolution: Fixed
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Jira needs a specific collation to make things work.
We should have a check that for every DB Engine the proper collation is used.
If not a BIG message should be written in the logs stating that some functionalities are not going to work because of this.
For the different DBs the collations are :
- Oracle : BINARY
- Mysql: utf8_bin
- Postgres : C or POSIX
- SQL Server : SQL_Latin1_General_CP437_CI_AI or SQL_Latin1_General_CI_AI
- HSQLDB : TBD
- causes
-
JRASERVER-43761 Collation check for Oracle is looking incorrectly at NLS_CHARACTERSET instead of NLS_SORT
-
- Closed
-
- is related to
-
JSWSERVER-11178 Unable to rank with any database collation that does not order all alphanumeric characters the same as ASCII
-
- Closed
-
- relates to
-
JRACLOUD-39970 Jira needs to check the collation of the DB before it starts
- Closed
- supersedes
-
JSWSERVER-11169 Fixing NLS_SORT for Jira Agile queries
-
- Closed
-
[JRASERVER-39970] Jira needs to check the collation of the DB before it starts
Workflow | Original: JAC Suggestion Workflow [ 3051982 ] | New: JAC Suggestion Workflow 3 [ 3680803 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2614298 ] | New: JAC Suggestion Workflow [ 3051982 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2577958 ] | New: Confluence Workflow - Public Facing v4 [ 2614298 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2357399 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2577958 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2124763 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2357399 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2087165 ] | New: JIRA Bug Workflow w Kanban v6 [ 2124763 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 890314 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2087165 ] |
Description |
Original:
Jira needs a specific collation to make things work.
We should have a check that for every DB Engine the proper collation is used. If not a BIG message should be written in the logs stating that some functionalities are not going to work because of this. For the different DBs the collations are : * Oracle : BINARY * Mysql: utf8_bin * Postgres : C or POSIX * SQL Server : SQL_Latin1_General_CP437_CI_AI or SQL_Latin1_General_CI_AI * HSQLDB : TBD |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-39970]. {panel} Jira needs a specific collation to make things work. We should have a check that for every DB Engine the proper collation is used. If not a BIG message should be written in the logs stating that some functionalities are not going to work because of this. For the different DBs the collations are : * Oracle : BINARY * Mysql: utf8_bin * Postgres : C or POSIX * SQL Server : SQL_Latin1_General_CP437_CI_AI or SQL_Latin1_General_CI_AI * HSQLDB : TBD |
Link |
New:
This issue relates to |
Labels | Original: Fug expedite | New: Fug affects-server expedite |