New answers tagged

0

I only skimmed through the answers, so I might have missed a similar answer. The idea is to use a generated column that is either the p.k or a constant that does not exist as a value for the p.k. create table foo ( bar int not null primary key , chk char(1) check (chk in('Y', 'N')) , some_name generated always as ( case when chk = 'N' ...


2

Here's a solution for MySQL and MariaDB using virtual columns that's a bit more elegant. It requires MySQL >= 5.7.6 or MariaDB >= 5.2: MariaDB [db]> create table foo(bar varchar(255), chk boolean); MariaDB [db]> describe foo; +-------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +-------+------...


-3

Option Name Description NLS_LANG The current language, territory, and database character set, which are determined by session-wide globalization parameters. NLS_LANGUAGE The current language for the session. NLS_SORT The sequence of character values used when sorting or comparing text. To check the current NLS settings, type: select * from v$...


29

TL;DR There is no such thing as a "vendor-agnostic" view of Collations, nor even "version-agnostic", since their implementations -- including which aspects can be made insensitive and their naming conventions -- are vendor-specific and change over time. Here is a summary of what I have found, and the details are in the longer section below the line: RDBMS ...



Top 50 recent answers are included