unicode strings, by changing the default collation settings
(which is latin1 or windows' 1252 encoding or whatever it is). If
you're working with a table, when columns are N* column types, it will
work fine.
-Ken
On Tue, Apr 4, 2017 at 4:20 AM, Kenneth Shaw wrote:
> This doesn
option.
-Ken
On Tue, Apr 4, 2017 at 4:08 AM, Karsten Hilbert wrote:
> On Tue, Apr 04, 2017 at 03:48:16AM +0700, Kenneth Shaw wrote:
>
>> It should work. What database did you try that with? I haven't tried
>> to do heavy / extensive utf8 tests, but all of Go (including the
&
On Mon, Apr 3, 2017 at 8:51 PM, Merlin Moncure wrote:
> Wow! this is _fantastic_. I use "sqsh" for connecting to sql server
> -- this is already a significant improvement in many ways (based on
> playing around for around 10 minutes). This app would fill a real
> need for me. Here is some feedb
hing usable.
** for certain definitions of "very soon"
-Ken
On Sun, Apr 2, 2017 at 8:36 PM, Andy Colson wrote:
> On 04/02/2017 07:55 AM, Kenneth Shaw wrote:
>>
>> Hi All,
>>
>>
>> usql is built in Go, and as of today supports all the major databas
Hi All,
I apologize in advance if this is somewhat off-topic, but I thought I
would inform the people (ie, psql users) about usql, a
universal-command line tool that aims to work the same way psql does,
but with every database (not just PostgreSQL).
usql is built in Go, and as of today supports a
