Subject | RE: [firebird-support] hello, can someone translate the follow error messages? ref/eDN8022297953 |
---|---|
Author | dennis |
Post date | 2008-01-09T13:35:16Z |
Thank you Aage
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Aage Johansen
Sent: Tuesday, January 08, 2008 10:18 PM
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] hello, can someone translate the follow
error messages? ref/eDN8022297953
dennis wrote:
your old one).
eventually.
CommitRetaining is fine, but not always. You will have to find some
points in your applications where you do a commit, and maybe just
refresh your screen by closing/opening queries.
problems out of sight.
--
Aage J.
[Non-text portions of this message have been removed]
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Aage Johansen
Sent: Tuesday, January 08, 2008 10:18 PM
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] hello, can someone translate the follow
error messages? ref/eDN8022297953
dennis wrote:
>> ...database
>
> Is "safe restore" you mentioned something special that the classic
> restore? Does it have any extra setting?I guess Helen meant to restore to a new database (not overwriting
>
your old one).
>runs
>
> In the application I use only the CommitRetaining. I do CommitRetaining
> after each post and I do CommitRetaining instead of Commit in order remain
> the dataset opened after each post. I do not start and commit the
> transaction because after each one post I do a commit. This application
> on pos machines 3 years now, I haven't face problems in transaction layerNot doing commit (only CommitRetaining) will get you into trouble,
> with this mechanism. I do not say that is the most right way but is a
> mechanism that covers what we want from the application, the direct update
> of the database. Is something wrong with that with this way?
>
eventually.
CommitRetaining is fine, but not always. You will have to find some
points in your applications where you do a commit, and maybe just
refresh your screen by closing/opening queries.
>Maybe the level of activity, usage pattern, hardware resources kept
>
> The most strange thing is that in other branches, the same application has
> not problem at all. But I am still investigating
>
problems out of sight.
--
Aage J.
[Non-text portions of this message have been removed]