PC SOFT

ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

Home | Sign in | English EN
  • Error cases
  • Handling records during a transaction
  • Transactions and independent HFSQL context
  • OLE DB and Native Connectors
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Others
Stored procedures
Validates the current transaction:
AndroidAndroid Widget iPhone/iPadIOS WidgetMac Catalyst The management of transactions is available for HFSQL Client/Server databases.
Versions 17 and later
iPhone/iPad This function is now available for iPhone/iPad applications.
New in version 17
iPhone/iPad This function is now available for iPhone/iPad applications.
iPhone/iPad This function is now available for iPhone/iPad applications.
Versions 18 and later
Universal Windows 10 App This function is now available in Windows Store apps mode.
Android Widget This function is now available in Android widget mode.
Java This function is now available for Java applications.
Android This function is now available for Android applications.
New in version 18
Universal Windows 10 App This function is now available in Windows Store apps mode.
Android Widget This function is now available in Android widget mode.
Java This function is now available for Java applications.
Android This function is now available for Android applications.
Universal Windows 10 App This function is now available in Windows Store apps mode.
Android Widget This function is now available in Android widget mode.
Java This function is now available for Java applications.
Android This function is now available for Android applications.
Remark: From version 19, HFSQL is the new name of HyperFileSQL.
Versions 21 and later
Universal Windows 10 App This function is now available in Universal Windows 10 App mode.
New in version 21
Universal Windows 10 App This function is now available in Universal Windows 10 App mode.
Universal Windows 10 App This function is now available in Universal Windows 10 App mode.
Example
MaConnexion1 est une Connexion
 
// Début de la transaction sur les fichiers de données associés à la connexion MaConnexion1
MaConnexion1.TransactionDébut()
 
// Code permettant de préparer la commande à ajouter
// ...
 
QUAND EXCEPTION DANS
// Ajout de la commande
Commande.Ajoute()
// Validation de l'ajout
MaConnexion1.TransactionFin()
FAIRE
// Suppression des lignes de commandes
MaConnexion1.TransactionAnnule()
FIN
Syntax

Validating a transaction in progress on a connection Hide the details

<Result> = <Connection>.TransactionEnd()
<Result>: Boolean
  • True if the transaction is ended,
  • False if a problem occurred. The HErrorInfo function provides more information about the error.
Caution: The function has no effect if a global transaction is started. The syntax 2 must be used.
<Connection>: Connection variable
Name of the Connection variable that describes the connection to use.

Validating a global transaction in progress Hide the details

<Result> = TransactionEnd()
<Result>: Boolean
  • True if the transaction is ended,
  • False if a problem occurred. The HErrorInfo function provides more information about the error.
Remarks

Error cases

  • Nesting transactions: Transactions cannot be nested (that is, function <Connection variable>.TransactionStart or function <Connection variable>.Transaction cannot be called within a transaction). In this case, error 70031 occurs.
  • Versions 19 and later
    A fatal error is displayed in the following cases:
    • A transaction is started on all the connections while there is at least one connection in transaction.
    • A transaction is started on a connection while a transaction was already started on all the connections.
    • A transaction is started on all the connections while there is at least one connection whose isolation mode is not "Read Uncommitted".
    New in version 19
    A fatal error is displayed in the following cases:
    • A transaction is started on all the connections while there is at least one connection in transaction.
    • A transaction is started on a connection while a transaction was already started on all the connections.
    • A transaction is started on all the connections while there is at least one connection whose isolation mode is not "Read Uncommitted".
    A fatal error is displayed in the following cases:
    • A transaction is started on all the connections while there is at least one connection in transaction.
    • A transaction is started on a connection while a transaction was already started on all the connections.
    • A transaction is started on all the connections while there is at least one connection whose isolation mode is not "Read Uncommitted".

Handling records during a transaction

During a transaction, some rules must be complied with when handling the records. For more details, see Transactions: Handling records during a transaction.

Transactions and independent HFSQL context

When copying a context, if a transaction is in progress on the first context, the new context is not in transaction. You must call <Connection variable>.TransactionStart (or <Connection variable>.Transaction) to start a transaction in the new context.
WINDEVWEBDEV - Server codeOLE DBNative Connectors (Native Accesses)

OLE DB and Native Connectors

Only syntaxes with connection are taken into account by the Native Connectors (also called Native Accesses) that support transactions. You can also use SQLTransaction.
Component: wd270hf.dll
Minimum version required
  • Version 25
This page is also available for…
Comments
Click [Add] to post a comment