replace funcion with utf-8 extrange behaviour
-
Key: CORE-4599
URL: http://tracker.firebirdsql.org/browse/CORE-4599
Project: Firebird Core
Issue Type: Bug
Components: Charsets/Collation
Hello, All.
I've changed parse.y with attached diff, but even after clean full rebuild isql shows
me this error:
SQL set transaction no replication;
Commit current transaction (y/n)?n
Rolling back work.
Statement failed, SQLSTATE = 42000
Dynamic SQL Error
-SQL error code = -104
-Token
On 07/11/2014 14:03, Dimitry Sibiryakov wrote:
Hello, All.
I've changed parse.y with attached diff, but even after clean full
rebuild isql shows me this error:
SQL set transaction no replication;
Commit current transaction (y/n)?n
Rolling back work.
Statement failed, SQLSTATE = 42000
Dimitry,
SQL set transaction no replication;
Commit current transaction (y/n)?n
Rolling back work.
Statement failed, SQLSTATE = 42000
Dynamic SQL Error
-SQL error code = -104
-Token unknown - line 1, column 20
-replication
Are you proposing to make this change (adding no replication
07.11.2014 17:07, Adriano dos Santos Fernandes wrote:
Was not added it to keywords.cpp?
Yep, that is the trick. Thanks.
--
WBR, SD.
--
Firebird-Devel mailing list, web interface at
07.11.2014 17:18, Leyne, Sean wrote:
Are you proposing to make this change (adding no replication syntax) to the
Firebird codebase?
So far it is a private fork. But, according to the IDPL license, you can
merge changed
sources to the main codebase if you wish as soon as they are
On Fri, 07 Nov 2014 17:21:51 +0100, Dimitry Sibiryakov s...@ibphoenix.com
wrote:
07.11.2014 17:18, Leyne, Sean wrote:
Are you proposing to make this change (adding no replication syntax)
to the Firebird codebase?
So far it is a private fork. But, according to the IDPL license, you
can
On 11/6/2014 10:40 AM, Dimitry Sibiryakov wrote:
Hello, All.
I wonder if SQL standard says something about syntax of transaction's
option for
disabling replication of changes made by this transaction?
I might be wrong, but I think this whole topic needs a more than a bit
more
07.11.2014 19:58, Jim Starkey wrote:
Statement level multi-master replication is basically
impossible to get right, so you need to pick among a set of bad
options. There about a billion things that can go wrong (consider a
timestamp or random number generator, for example) that requires
