Amit Langote
amitl****@gmail*****
2013年 11月 7日 (木) 15:43:57 JST
On Thu, Nov 7, 2013 at 2:45 PM, Beena Emerson <memis****@gmail*****> wrote: > Hello, > > On Wed, Sep 11, 2013 at 6:09 PM, Beena Emerson <memis****@gmail*****> > wrote: >> >> Hello All, >> >> The pg_bigm document states that pg_bigm can work with only UTF8 encoding. >> However, there does not seem to be any problems when pg_bigm is used with >> other encodings. > > > Now, the locale and encoding restriction have been removed. > >> >> >> Please find attached a patch which adds regression tests to test pg_bigm >> functions for LATIN1 and EUC_JP encoding. >> >> New files with appropriate encoding have been created to test pg_bigm in >> database with different encoding. > > > I just wanted to confirm if there is any plan of adding the regression tests > to test pg_bigm in other locales and encoding. > > If yes, then please check the attached patch. The patch sent before has been > rebased. > Hey, how about using something like sv_SE.iso88591 locale for latin1 regression tests? So, sql/latin1.sql +CREATE DATABASE latin1_regression ENCODING = 'LATIN1' LC_CTYPE='sv_SE LC_COLLATE='sv_SE' TEMPLATE template0; or +CREATE DATABASE latin1_regression ENCODING = 'iso88591' LC_CTYPE='sv_SE' LC_COLLATE='sv_SE' TEMPLATE template0; What do you think? -- Amit
Fork