/
balmaster
/
postgres
Обзор
Документация
Войти
/
balmaster
/
postgres
Код
Запросы
0
Задачи
Вики
Пакеты
0
Релизы
0
Аналитика
Безопасность
master
src/pl/tcl/sql/pltcl_unicode.sql
43 строки
1 KB
Noah Misch
EUC_CN, EUC_JP, EUC_KR, EUC_TW: Skip U+00A0 tests instead of failing.
26 фев 2026, 05:13
26 фев 2026, 05:13
0163951
Код
Авторство
О чём код?
-- -- Unicode handling -- -- This test case would fail if the database encoding is EUC_CN, EUC_JP, -- EUC_KR, or EUC_TW, for lack of any equivalent to U+00A0 (no-break space) in -- those encodings. However, testing with plain ASCII data would be rather -- useless, so we must live with that. -- SELECT getdatabaseencoding() IN ('EUC_CN', 'EUC_JP', 'EUC_KR', 'EUC_TW') AS skip_test \gset \if :skip_test \quit \endif SET client_encoding TO UTF8; CREATE TABLE unicode_test ( testvalue text NOT NULL ); CREATE FUNCTION unicode_return() RETURNS text AS $$ return "\xA0" $$ LANGUAGE pltcl; CREATE FUNCTION unicode_trigger() RETURNS trigger AS $$ set NEW(testvalue) "\xA0" return [array get NEW] $$ LANGUAGE pltcl; CREATE TRIGGER unicode_test_bi BEFORE INSERT ON unicode_test FOR EACH ROW EXECUTE PROCEDURE unicode_trigger(); CREATE FUNCTION unicode_plan1() RETURNS text AS $$ set plan [ spi_prepare {SELECT $1 AS testvalue} [ list "text" ] ] spi_execp $plan [ list "\xA0" ] return $testvalue $$ LANGUAGE pltcl; SELECT unicode_return(); INSERT INTO unicode_test (testvalue) VALUES ('test'); SELECT * FROM unicode_test; SELECT unicode_plan1();