I figured out that I need to use the function CHR to enter supplementary
unicode characters (code points > , i.e. planes 1 - F), e.g.
insert into unicode(id, string) values(100, CHR(128120)); -- a mojo
character, https://unicodelookup.com/#0x1f478/1
insert into unicode(id, string) values(101,
eturns the correct values for
all supported unicode chars. Correct sorting is nice-to-have.
Any help to get unicode chars, particularly the mojos (0x1F478, 0x1F479), in
and out of pg correctly is much appreciated. Thank you!
James
On Tue, Dec 20, 2016 at 9:24 PM, Tom Lane wrote:
> James
Unicode has evolved from version 1.0 with 7,161 characters released in 1991
to version 9.0 with 128,172 characters released in June 2016. My questions
are
- which version of Unicode is supported by PostgreSQL 9.6.1?
- what does "supported" exactly mean? simply store it? comparison? sorting?
substri
Thank you, John.
On Dec 2, 2016 23:12, "John R Pierce" wrote:
> On 12/2/2016 10:37 PM, James Zhou wrote:
>
>> I am new to PostgreSQL and am leaning it. I installed PostgreSQL on a
>> Windows 7 laptop and would like to play with pgbench to generate a sample
>> d
Hi,
I am new to PostgreSQL and am leaning it. I installed PostgreSQL on a
Windows 7 laptop and would like to play with pgbench to generate a sample
database and a bit load.
As I read, pgbench should come with the server download. But after I
install it, I could find pgbench:
[image: Inline image
