| Subject | Re: [firebird-support] Problem querying MON$STATEMENTS table |
|---|---|
| Author | |
| Post date | 2016-09-16T06:56Z |
Hello
On Friday, September 16, 2016 3:47 AM, "Helen Borrie helebor@... [firebird-support]" <firebird-support@yahoogroups.com> wrote:
Friday, September 16, 2016, 12:02:28 AM, Gregor Kobler wrote:
Once the SELECT statement has finished fetching, its state is no
longer active...it becomes "idle".
cursor restarts.
Both of those fields will hold values only while the statement is
active. A statement that is idle is not active.
If you suspect a bug, please try to give a proper description of what
you mean by "working well" and "not working" and post it, with your
statements, to firebird-devel. Also give the build number of the
snapshot that you refer to as "Server 3.0.1", as these snapshots are
refreshed very regularly.
The core devs have been working pretty solidly on Fb3 bugs over the
past 3 months so you should be able to discover what kind of a problem
(if any) you are actually observing and whether it is fixed.
HB
> I have a problem when i querying the MON$STATEMENS table on Server 2.5.5 and also 2.5.6Open output set <> active query.
>
> Do the follow steps:
>
> Open a connection to the database, then start a transaction an open
> a table to show the content and keep it open/active Now run the
> follow statement "SELECT * FROM MON$STATEMENS"
>
> The Row that should shows you the active query are not correct!
Once the SELECT statement has finished fetching, its state is no
longer active...it becomes "idle".
>Zero is the "idle" state. It will go to "active" (1) next time the
> The column MON$STATE shows allways Zero
cursor restarts.
> and also the columns
> MON$TRANSACTION_ID and MON$TIMESTAMP are also allways NULL!!
Both of those fields will hold values only while the statement is
active. A statement that is idle is not active.
>
> The Server 3.0.1 are not affected on this problem.
>
> The follow databases with charset are not working (tested) NONE, WIN1250, ISO8859_1
>
> A database with charset WIN1251 are working well.
>
> May this could be a bug.
If you suspect a bug, please try to give a proper description of what
you mean by "working well" and "not working" and post it, with your
statements, to firebird-devel. Also give the build number of the
snapshot that you refer to as "Server 3.0.1", as these snapshots are
refreshed very regularly.
The core devs have been working pretty solidly on Fb3 bugs over the
past 3 months so you should be able to discover what kind of a problem
(if any) you are actually observing and whether it is fixed.
HB