Subject | Re: [firebird-support] using Firebird mga from Access |
---|---|
Author | Milan Babuskov |
Post date | 2011-05-31T09:39:54Z |
heineferreira wrote:
using MGA, because Firebird is MGA-only, you can't turn it off even if
you wanted.
happens. You will be surprised. In the end, the only thing that needs to
be handled is concurrent updates to the same record - in this case you
need to handle the failed update (for NO_WAIT) transactions, or a
deadlock timeout (for WAIT) transactions.
If your application requires locking for it's own functioning you can
lock the desired records by issuing a dummy update statement like:
UPDATE table1 SET column1 = column1 WHERE id = :desired_id;
--
Milan Babuskov
==================================
The easiest way to import XML, CSV
and textual files into Firebird:
http://www.guacosoft.com/xmlwizard
==================================
> Do you know if it's possible to use the MGA with ADO or DAO?Either. Just test if it works at all. If it does work, then you are
using MGA, because Firebird is MGA-only, you can't turn it off even if
you wanted.
> adding a "no lock" into the select statementNo need to, Firebird's SELECTs are NO LOCK by default.
> Do you know of a way to achieve this?Try simply using the system without worrying about locking and see what
happens. You will be surprised. In the end, the only thing that needs to
be handled is concurrent updates to the same record - in this case you
need to handle the failed update (for NO_WAIT) transactions, or a
deadlock timeout (for WAIT) transactions.
If your application requires locking for it's own functioning you can
lock the desired records by issuing a dummy update statement like:
UPDATE table1 SET column1 = column1 WHERE id = :desired_id;
--
Milan Babuskov
==================================
The easiest way to import XML, CSV
and textual files into Firebird:
http://www.guacosoft.com/xmlwizard
==================================