On 18/07/11 14:37, Dmitry Yemanov wrote:
> SHOW commands operate on a separate transaction from user statements.
> They run as READ COMMITTED background statements and acknowledge all
> metadata changes immediately.
Thanks. I've updated the isql manual with these details.
Cheers,
Norm.
--
Norman
18.07.2011 16:51, Paul Vinkenoog wrote:
>
>> You can use various SHOW commands in isql to query database metatdata.
>> Metatdata is stored in system tables. When a SHOW command is issued,
>> isql commits the current transaction and begins a new one, in READ
>> COMMITTED isolation.
>
> As you showed
Hi Norman,
> You can use various SHOW commands in isql to query database metatdata.
> Metatdata is stored in system tables. When a SHOW command is issued,
> isql commits the current transaction and begins a new one, in READ
> COMMITTED isolation.
As you showed below, this is not (always) true. Ma
Afternoon all,
I'm doing a bit of lunchtime work on the isql manual (hooray!) and I've
come across this bit in the existing version, in the Transaction
Handling section:
You can use various SHOW commands in isql to query database metatdata.
Metatdata is stored in system tables. When a SHOW c
14.07.2011 18:55, Norman Dunbar wrote:
> So it seems as if it wasn't quite ready for publication as it would
> break the pdf version.
Just for the record, this is how it currently looks in PDF:
http://www.firebirdsql.org/file/documentation/reference_manuals/user_manuals/Firebird-isql.pdf
Dmitr
Hi Paul,
On 10/07/11 00:50, Paul Vinkenoog wrote:
> Do you know why the isql guide was never published until now? It seems you
> updated it in October 2009 - wasn't it ready yet?
Sorry, been away for a few days, just back. Been in Dorset sampling
cider! ;-)
As far as I can recall, I've never up
Hi Norman,
Do you know why the isql guide was never published until now? It seems you
updated it in October 2009 - wasn't it ready yet?
Paul
--
All of the data generated in your IT infrastructure is seriously valuable.
