-Original Message-
From: Dmitry Yemanov [mailto:firebi...@yandex.ru]
Sent: Martes, 08 de Abril de 2014 2:12
Extending an idea it would be good to rename all such
constants in the
same manner. No?
Perhaps. But formally, BLR is a part of the public API, such a change
can
Unfortunately, rdb$backup_history is the only sys gen that's not modified
from an internal request.
Time to use triggers and INSERT RETURNING ? :)
Regards,
Vlad
--
Put Bad Developers to Shame
Dominate Development
-Original Message-
From: Vlad Khorsun [mailto:hv...@users.sourceforge.net]
Sent: Martes, 08 de Abril de 2014 2:38
Unfortunately, rdb$backup_history is the only sys gen
that's not modified
from an internal request.
Time to use triggers and INSERT RETURNING ? :)
Or let
Unfortunately, rdb$backup_history is the only sys gen
that's not modified
from an internal request.
Time to use triggers and INSERT RETURNING ? :)
Or let VIO_store() handle rel_backup_history and do the generator increment
from set_metadata_id().
Agree.
Regards,
Vlad
-Original Message-
From: Vlad Khorsun [mailto:hv...@users.sourceforge.net]
Sent: Martes, 08 de Abril de 2014 3:06
Unfortunately, rdb$backup_history is the only sys gen
that's not modified
from an internal request.
Time to use triggers and INSERT RETURNING ? :)
Unfortunately, rdb$backup_history is the only sys gen
that's not modified
from an internal request.
Time to use triggers and INSERT RETURNING ? :)
Or let VIO_store() handle rel_backup_history and do the
generator increment
from set_metadata_id().
Agree.
In
08.04.2014 11:54, Vlad Khorsun wrote:
Personally, i not consider it as important,
if nbackup v3 will not work with Firebird before v3...
Me neither. But if it can be easily done, why not.
Dmitry
--
Put Bad
On 04/08/14 11:30, Claudio Valderrama C. wrote:
-Original Message-
From: Alex Peshkoff [mailto:peshk...@mail.ru]
Sent: Lunes, 07 de Abril de 2014 11:53
Hi all!
nbackup in trunk is broken:
fbs bin # ./nbackup -b 0 employee l0.nbk
[
PROBLEM ON execute history insert.
System
On 04/05/14 16:44, Simonov Denis wrote:
The final assembly firebird 3.0.0.31021-0 found the following problems .
After the implementation of CORE- 3370 it became impossible to connect to
the database already created . Well here it is clear changed ODS, decided
to recreate the database from
IStatement::execute() and IAttachment::execute() functions should return on
error pointer to old transaction interface
--
Key: CORE-4387
URL:
Alex et al,
May I ask to rethink namings, please? Things like RDB$MAP or
/jrd/Mapping.cpp sound very confusing. What is mapped to what? Maybe
Mapping.cpp is about memory mapped files?
I'd suggest at least RDB$USER_MAP and UserMapping.cpp instead. Maybe
someone else will have a better
Alex et al,
May I ask to rethink namings, please? Things like RDB$MAP or
/jrd/Mapping.cpp sound very confusing. What is mapped to what? Maybe
Mapping.cpp is about memory mapped files?
I'd suggest at least RDB$USER_MAP and UserMapping.cpp instead. Maybe
someone else will have a better
On 04/08/2014 11:41 PM, Leyne, Sean wrote:
Alex et al,
May I ask to rethink namings, please? Things like RDB$MAP or
/jrd/Mapping.cpp sound very confusing. What is mapped to what? Maybe
Mapping.cpp is about memory mapped files?
I'd suggest at least RDB$USER_MAP and UserMapping.cpp instead.
Folks, sorry for nitpicking, but I don't like this alias in
classes\InternalMessageBuffer.h:
typedef ArrayUCHAR Buffer; // May be it will become a class in the future,
but now it is just a plain array
because Buffer is a name too general. It's not in a cpp, it's in a header
included in other
Ability to specify the step for generators / sequences is very good. But I
think the syntax would be much closer to the standard. So in Oracle / MS
SQL / Postgresql step instructions for using the keyword INCREMENT BY
instead STEP
CREATE SEQUENCE name [INCREMENT [BY] increment]
-Original Message-
From: Simonov Denis [mailto:sim-m...@list.ru]
Sent: Miércoles, 09 de Abril de 2014 1:27
Ability to specify the step for generators / sequences is
very good. But I
think the syntax would be much closer to the standard. So in
Oracle / MS
SQL / Postgresql
On 04/09/2014 10:14 AM, Claudio Valderrama C. wrote:
Folks, sorry for nitpicking, but I don't like this alias in
classes\InternalMessageBuffer.h:
typedef ArrayUCHAR Buffer; // May be it will become a class in the future,
but now it is just a plain array
because Buffer is a name too general.
17 matches
Mail list logo
