[Properties (by Name)] [Methods (by Name)]
Postgres differs from Firebird in ways relevant to MSEgui
Source position: msepqconnection.pas line 44
type tmsepqconnection = class(TPQConnection,idbcontroller) |
public |
constructor create(); override; |
published |
property DatabaseName: filenamety; [rw] |
property Connected: Boolean; [rw] |
property options: pqconnectionoptionsty; [rw] |
end; |
|
Postgres differs from Firebird in ways relevant to MSEgui |
|
| | | ||
| | | ||
| | | ||
| | | ||
| | | ||
| | | ||
| | | ||
| | | ||
TObject |
Postgres differs from Firebird in ways relevant to MSEgui: there is no native CommitRetaining, MSEgui simulates it by opening a new transaction without refreshing the datasets; there are no named transactions, every transaction has its own connection; blobs are fetched with the record (not on demand, see bdo_cacheblobs); and a failed statement aborts the whole transaction (a rollback is required to continue) — pqco_usesavepoint masks this by wrapping every statement in a SAVEPOINT, at the cost of an extra round-trip per statement.