de.ipcon.db.core

Interface ServerLocalTransactionI

All Superinterfaces:

java.lang.AutoCloseable

All Known Implementing Classes:

ServerLocalTransaction

public interface ServerLocalTransactionI
extends java.lang.AutoCloseable

Field Summary

Fields

Modifier and Type	Field and Description
static java.lang.String	$0

Method Summary

Modifier and Type	Method and Description
void	closeNT() Closes this ServerLocalTransactionI, relinquishing any underlying resources, logging errors only instead of throwing them.
Transaction	getTransaction() Returns the underlying Transaction that is used for recording server local changes.
boolean	isClosed() Returns true if this ServerLocalTransaction is closed and thus not usable anymore.
default TransactionAnswer	saveBO() Persists the changes recorded in this ServerLocalTransactionI to the database.
TransactionAnswer	saveBO(Benutzer saveAs) Persists the changes recorded in this ServerLocalTransactionI to the database.
default void	saveBOWithoutLogs() Persists the changes recorded in this ServerLocalTransactionI to the database, but does not record the changes via BT/BP logs.
void	saveBOWithoutLogs(Benutzer saveAs) Persists the changes recorded in this ServerLocalTransactionI to the database, but does not record the changes via BT/BP logs.

Methods inherited from interface java.lang.AutoCloseable

close

Field Detail

$0

static final java.lang.String $0

See Also:

Constant Field Values

Method Detail

getTransaction

Transaction getTransaction()

Returns the underlying Transaction that is used for recording server local changes.

Returns:

the underlying Transaction that is used for recording server local changes.

saveBO

default TransactionAnswer saveBO()

Persists the changes recorded in this ServerLocalTransactionI to the database. Retries are not supported, as a failed save is broken and can and must not be retried. You need to recreate the Transaction and try saving again with a fresh ServerLocalTransactionI. It is discouraged to retry saving the same procs again, as they were based on outdated data. Simply saving those procs would probably be wrong, as operating on a different state will most probably yield a different result to save. So it is much better and safer to operate on the obviously modified new database state. Thus the core does not support retries and you need to care for that in your own code.

Returns:

the TransactionAnswer resulting from the save process, or null if no saving was actually done for some reason

saveBO

TransactionAnswer saveBO(Benutzer saveAs)

Persists the changes recorded in this ServerLocalTransactionI to the database. Retries are not supported, as a failed save is broken and can and must not be retried. You need to recreate the Transaction and try saving again with a fresh ServerLocalTransactionI. It is discouraged to retry saving the same procs again, as they were based on outdated data. Simply saving those procs would probably be wrong, as operating on a different state will most probably yield a different result to save. So it is much better and safer to operate on the obviously modified new database state. Thus the core does not support retries and you need to care for that in your own code.

Parameters:

saveAs - the Benutzer to save on behalf of

Returns:

the TransactionAnswer resulting from the save process, or null if no saving was actually done for some reason

saveBOWithoutLogs

default void saveBOWithoutLogs()

Persists the changes recorded in this ServerLocalTransactionI to the database, but does not record the changes via BT/BP logs. This might be useful, if the caller does not want to write logs (saving with DBMan), but only persist the changes (ph.commit), e.g. LagerBestandNachlaeufer (no logs as the changes must not be synced). Retries are not supported, as a failed save is broken and can and must not be retried. You need to recreate the Transaction and try saving again with a fresh ServerLocalTransactionI. It is discouraged to retry saving the same procs again, as they were based on outdated data. Simply saving those procs would probably be wrong, as operating on a different state will most probably yield a different result to save. So it is much better and safer to operate on the obviously modified new database state. Thus the core does not support retries and you need to care for that in your own code.

saveBOWithoutLogs

void saveBOWithoutLogs(Benutzer saveAs)

Persists the changes recorded in this ServerLocalTransactionI to the database, but does not record the changes via BT/BP logs. This might be useful, if the caller does not want to write logs (saving with DBMan), but only persist the changes (ph.commit), e.g. LagerBestandNachlaeufer (no logs as the changes must not be synced). Retries are not supported, as a failed save is broken and can and must not be retried. You need to recreate the Transaction and try saving again with a fresh ServerLocalTransactionI. It is discouraged to retry saving the same procs again, as they were based on outdated data. Simply saving those procs would probably be wrong, as operating on a different state will most probably yield a different result to save. So it is much better and safer to operate on the obviously modified new database state. Thus the core does not support retries and you need to care for that in your own code.

Parameters:

saveAs - the Benutzer to save on behalf of

closeNT

void closeNT()

Closes this ServerLocalTransactionI, relinquishing any underlying resources, logging errors only instead of throwing them.

isClosed

boolean isClosed()

Returns true if this ServerLocalTransaction is closed and thus not usable anymore.

Returns:

true if this ServerLocalTransaction is closed