|
So for TIBQuery and TIBSQL should I be doing anything when using select
statements to ensure that the transaction is read only or is it only an
issue when using tables? I don't know what you mean by "mark the
transaction inside the query appropriately" since there are no
properties for specifying a transaction as read only. Phil. Rohit Gupta wrote: A readonly table is RO for the end user but not as far as the Firebird is concerned. It looks at the transaction type. You can do a select with a normal default transaction that IBO or IBX or whatever put on. This is what most people do when they start. But this is not read only... it leaves the transaction open for edit/insert/delete.You need to mark the transaction inside the table/query appropriately. I dont remember the official names as we always use subclassed components. In these we make the table.readonly do the right thing. We also rename the IBO's IB_Transaction to Transaction to make it more component neutral. We also allocate a new transaction inside it if it has not been assigned by the programmer. So that it never uses the default transaction. Date sent: Thu, 28 Jul 2005 10:48:08 +1200 From: Phil Middlemiss <[EMAIL PROTECTED]> Organization: MTS Ltd To: NZ Borland Developers Group - Delphi List <[email protected]> Subject: Re: [DUG] Firebird connections / queries / transactions Send reply to: NZ Borland Developers Group - Delphi List <[email protected]> <mailto:[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED]> [ Double-click this line for list subscription options ] Thanks for the overview. By "read-only" transactions, are you referring to the SQL executed within a transaction? Your comment about the default transaction not being read-only has me puzzled - isn't it the table itself that is readonly? Phil. Rohit Gupta wrote: |
_______________________________________________ Delphi mailing list [email protected] http://ns3.123.co.nz/mailman/listinfo/delphi
