Re[2]: [Firebird-devel] gbak bytes vs. Kbytes

[Nickolay S. <sk...@bs...>]

Hello, Mike !

Tuesday, October 29, 2002, 4:14:51 PM, you wrote:

>> In an attempt to fix this once and for all (?), is anyone is aware of any
>> platform+compiler supported that do _not_ have 64-bit integers support.

> Forget it. I fixed it using C++ and ostringstream.

> But (isn't there always one), to make this work it needs another gbak
> message added to the message DB. It should look exactly like msg 176
> "closing file, committing, and finishing.  %ld bytes written" except that
> the format specifier should be a string ("%s).

> Could someone in the know please add this entry to table MESSAGES in
> msg.gdb, make a backup, commit it and notify of what NUMBER it got. It
> should probably become something like:

> CODE: 120281
> FAC_CODE: 12
> NUMBER: 281
> TEXT: "closing file, committing, and finishing. %s bytes written"
> ROUTINE: BACKUP_backup
> The rest of the fields NULL.

I prefer using enter_messages and modify_messages program. :)

I added several messages and one more statement type to support savepoints.
Savepoint support lives in skidder branch and my local source tree
and it even works when savepoints are used in global context. I didn't
finish support of savepoints in procedures and triggers yet because it
seems that i found several warped places in backout code (2-3
redundant savepoints are places around EACH statement now).
It needs careful review and modification and it will take several
working days to fix.

I make pick up this issue to my schedule, but my changes will be
merged with main source tree only in 2-3 weeks probably.

You know that merging of messages is completely manual thing. I can
commit my msg.gbak to the main branch to avoid confusion later if you
want to fix it yourself now.

> Thanks,

> /Mike

-- 
Best regards,
 Nickolay                             mailto:sk...@bs...