On 26 April 2015 at 23:52, swaxolez wrote:
> I get the feeling I might want to wait for the next point release before
> deploying on anything other than a test platform. In the meantime, I'll
> play
> around and see how it works.
In the mean time, take a look at the rest of the documentation fo
I get the feeling I might want to wait for the next point release before
deploying on anything other than a test platform. In the meantime, I'll play
around and see how it works. These are fantastic additions to a fantastic
database. Thanks for the good work!
--
View this message in context:
On 26 April 2015 at 10:05, swaxolez wrote:
> It's not clear to me but is selective replication working in BDR? Does
> anyone have any examples if so?
Yes, selective replication (using replication sets) is supported in the
current 0.9 stable series.
The documentation on replication sets is ver
On Sun, 26 Apr 2015 12:43:57 +0200
Oliver Elphick wrote:
> On Sun, 2015-04-26 at 12:39 +0200, Bjørn T Johansen wrote:
> >
> > CREATE COLLATION nb_NO (LOCALE = nb_NO.utf8)
> >
> > But then I get this:
> >
> > ERROR: could not create locale "nb_no.utf8": No such file or
> > directory
> > DETAIL
On Sun, 2015-04-26 at 12:39 +0200, Bjørn T Johansen wrote:
>
> CREATE COLLATION nb_NO (LOCALE = nb_NO.utf8)
>
> But then I get this:
>
> ERROR: could not create locale "nb_no.utf8": No such file or
> directory
> DETAIL: The operating system could not find any locale data for the
> locale name
On Sun, 26 Apr 2015 11:48:37 +0200
Oliver Elphick wrote:
> On Sun, 2015-04-26 at 11:09 +0200, Bjørn T Johansen wrote:
> > Ok, tried to run:
> >
> > alter table medlem alter column fornavn varchar(50) collate nb_NO.utf8
> >
> > But I just get:
> >
> > [Error Code: 0, SQL State: 42601] ERROR:
On Sun, 2015-04-26 at 11:09 +0200, Bjørn T Johansen wrote:
> Ok, tried to run:
>
> alter table medlem alter column fornavn varchar(50) collate nb_NO.utf8
>
> But I just get:
>
> [Error Code: 0, SQL State: 42601] ERROR: syntax error at or near "varchar"
> (tried without the varchar also..)
ALT
On Sun, 26 Apr 2015 10:59:10 +0200
Bjørn T Johansen wrote:
> On Sun, 26 Apr 2015 10:31:37 +0200
> "Gunnar \"Nick\" Bluth" wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Am 26.04.2015 um 10:02 schrieb Bjørn T Johansen:
> > > My databases looks like this...:
> > >
> > >
On Sun, 26 Apr 2015 10:31:37 +0200
"Gunnar \"Nick\" Bluth" wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am 26.04.2015 um 10:02 schrieb Bjørn T Johansen:
> > My databases looks like this...:
> >
> >
> > List of databases Name |Owner | Encoding | Collate
> > |Ct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 26.04.2015 um 10:02 schrieb Bjørn T Johansen:
> My databases looks like this...:
>
>
> List of databases Name |Owner | Encoding | Collate
> |Ctype| Access privileges
> --+--+--+-
On Sun, Apr 26, 2015 at 5:02 PM, Bjørn T Johansen wrote:
> And my problem is that I am using Norwegian in some tables and when using
> order by the sort order is not correct for the Norwegian letters..
> So my guestion is if it is possible to get the correct sort order without
> recreating all my
My databases looks like this...:
List of databases
Name |Owner | Encoding | Collate |Ctype| Access
privileges
--+--+--+-+-+---
dbname | owner
12 matches
Mail list logo
