Thanks for further explanation, Ann and Sean. I'm basically aware of those
differences between gbak and nbackup, but I should have noted that the OIT in
the original database is ok and moving forward.
> Nbackup takes physical snapshots of pages as they change. It wouldn't
> recognize a record
remk_1 skriver:
>
> The original database has all transaction numbers moving forward
> (there are all about the same +- 2). But when I do a level 0 nbackup
> backup and then restore it, the OIT in the restored database gets
> frozen. So although transactions numbers stay the same, there must be
Hi Kjell,
>
> Are you sure you unlock (in nbackup terms) the restored database after
> restore? If not, perhaps that's why the OIT is frozen?
>
> Note: The Nbackup process is lock - copy - unlock. This means the copy
> you make is actually locked, so when you restore it, the result is a
> I just made some nbackup tests (FB 2.5.2 SS, Windows XP) and noticed that
whenever I use it to restore a database, it's Oldest transaction (OIT) gets
stuck. It remains at the same value until next database sweep. Is it a bug
or a feature ?
I think the problem is here:
What nbackup do is
Hi Ivan,
> On first connect to copied database the state of this "active" transaction
> is changed to "rollback", thus it becomes your stuck OIT.
this would explain the issue. So it is as designed functionality of nbackup,
that probably can't be avoided, only workaround (run the sweep after res
Em 16/4/2013 11:09, skander_sp escreveu:
> May be obvious, but til now, i don't see how much unoptimized works the
> "field in subselect" syntax.
>
> I'm using it in some procedure, just right til now, after check they work in
> the worse unoptimized mode...
>
> example:
>
> select * from Table1
I get the error 'validation error for column DISCOUNTED, value
"***null***"At procedure ...'
The column definition is
DISCOUNTED D_BOOLEAN DEFAULT 'N' NOT NULL
So why wouldn't its value be set to N when I insert in to the table? Is
it because I'm explicitly trying to insert NULL for the column?
> I get the error 'validation error for column DISCOUNTED, value
> "***null***"At procedure ...'
> The column definition is
> DISCOUNTED D_BOOLEAN DEFAULT 'N' NOT NULL
> So why wouldn't its value be set to N when I insert in to the table? Is
> it because I'm explicitly trying to insert NULL f
Rick,
> Is it because I'm explicitly trying to insert NULL for the column?
As Ivan already responded, Yes
The rational is that DEFAULT only applies if the column is not listed in the
INSERT statement, by SQL standard.
Assigning a value of NULL is a direct/positive action, so the DEFAULT does
Hi all!
Can anyone please give me hint, advices about how to install Firebird on
Android device?
I'd like to create a small Android application that collects data (interview)
and when returning to the office it would upload the collected data to a
server. Direct database connection to the mai
10 matches
Mail list logo
