ODBC Library/en - Versionsgeschichte

Cg: /* SQL Queries */

2021-12-06T10:19:22Z

SQL Queries

← Nächstältere Version		Version vom 6. Dezember 2021, 10:19 Uhr
Zeile 30:		Zeile 30:
	The library provides additional actions which execute a parametrized SQL statement. These have addition input pins to fill in placeholders in a statement template.		The library provides additional actions which execute a parametrized SQL statement. These have addition input pins to fill in placeholders in a statement template.

			== DB Queries ==

			==== [ODBC] Get ODBC Info ====
			This and other info actions retrieve meta information about the ODBC version, the table names, columns, keys etc.

	<hr>		<hr>

Cg: /* SQL Queries */

2021-12-06T10:16:47Z

SQL Queries

← Nächstältere Version		Version vom 6. Dezember 2021, 10:16 Uhr
Zeile 27:		Zeile 27:

	Similar to the above, but the resulting rows are sent individually to the output pin. Thus, for every result, one output tuple is generated, and the receiving action will be triggered once for each.		Similar to the above, but the resulting rows are sent individually to the output pin. Thus, for every result, one output tuple is generated, and the receiving action will be triggered once for each.

			The library provides additional actions which execute a parametrized SQL statement. These have addition input pins to fill in placeholders in a statement template.


	<hr>		<hr>

Cg: /* [ODBC] Execute-StreamOut */

2021-12-06T10:15:05Z

[ODBC] Execute-StreamOut

← Nächstältere Version		Version vom 6. Dezember 2021, 10:15 Uhr
Zeile 26:		Zeile 26:
	==== [ODBC] Execute-StreamOut ====		==== [ODBC] Execute-StreamOut ====

	Similar to the above, but the resulting rows are sent individually to the output pin. Thus, for every result, one output ~~table~~ is generated, and the receiving action will be triggered once for each.		Similar to the above, but the resulting rows are sent individually to the output pin. Thus, for every result, one output tuple is generated, and the receiving action will be triggered once for each.

	<hr>		<hr>

Cg: /* [ODBC] Execute-StreamOut */

2021-12-06T10:14:02Z

[ODBC] Execute-StreamOut

← Nächstältere Version		Version vom 6. Dezember 2021, 10:14 Uhr
Zeile 28:		Zeile 28:
	Similar to the above, but the resulting rows are sent individually to the output pin. Thus, for every result, one output table is generated, and the receiving action will be triggered once for each.		Similar to the above, but the resulting rows are sent individually to the output pin. Thus, for every result, one output table is generated, and the receiving action will be triggered once for each.

	[[Datei:TypicalODBCUse.png\|mini\|Typical ODBC Setup]]
	<hr>		<hr>
	{{noprint\| 1=		{{noprint\| 1=

Cg: /* Introduction */

2021-12-06T10:13:21Z

Introduction

← Nächstältere Version		Version vom 6. Dezember 2021, 10:13 Uhr
Zeile 5:		Zeile 5:

	Make sure that ODBC has been installed and configured on your machine, when using ODBC actions (on most machines, this is already installed, and you have to define the mapping from logical database names to driver type, host, username etc. in a setup dialog). This is operating system specific and out of the scope of the expecco documentation. Please consult your administrator on how to setup the ODBC configuration.		Make sure that ODBC has been installed and configured on your machine, when using ODBC actions (on most machines, this is already installed, and you have to define the mapping from logical database names to driver type, host, username etc. in a setup dialog). This is operating system specific and out of the scope of the expecco documentation. Please consult your administrator on how to setup the ODBC configuration.

			[[Datei:TypicalODBCUse.png\|mini\|Typical ODBC Setup]]

	== Connecting / Disconnecting ==		== Connecting / Disconnecting ==

Cg: /* SQL Queries */

2021-12-06T10:12:26Z

SQL Queries

← Nächstältere Version		Version vom 6. Dezember 2021, 10:12 Uhr
Zeile 26:		Zeile 26:
	Similar to the above, but the resulting rows are sent individually to the output pin. Thus, for every result, one output table is generated, and the receiving action will be triggered once for each.		Similar to the above, but the resulting rows are sent individually to the output pin. Thus, for every result, one output table is generated, and the receiving action will be triggered once for each.

			[[Datei:TypicalODBCUse.png\|mini\|Typical ODBC Setup]]
	<hr>		<hr>
	{{noprint\| 1=		{{noprint\| 1=

Cg: /* [ODBC] Connect */

2021-12-06T10:07:36Z

[ODBC] Connect

← Nächstältere Version		Version vom 6. Dezember 2021, 10:07 Uhr
Zeile 10:		Zeile 10:
	==== [ODBC] Connect ====		==== [ODBC] Connect ====
	Establishes a connection to a database. You have to provide the logical name of the database, and possibly a user/password combination. The logical name is typically specified in your operating systems ODBC configuration dialog.		Establishes a connection to a database. You have to provide the logical name of the database, and possibly a user/password combination. The logical name is typically specified in your operating systems ODBC configuration dialog.
	Upon success, a session handle is written to the output pin. This is needed to further talk to the		Upon success, a session handle is written to the output pin. This is needed to further talk to the database, and should either be stored in a variable, or passed along a pin-connection to one of the query actions below.
	database, and either stored in a variable, or passed along a pin-connection to one of the query actions below.

	==== [ODBC] Disconnect ====		==== [ODBC] Disconnect ====

Cg: /* Introduction */

2021-12-06T10:06:49Z

Introduction

← Nächstältere Version		Version vom 6. Dezember 2021, 10:06 Uhr
Zeile 4:		Zeile 4:
	Almost every relational database provides an ODBC driver and is thus accessable.		Almost every relational database provides an ODBC driver and is thus accessable.

	Make sure that ODBC has been installed and configured on your machine, when using ODBC actions (on most machines, this is already installed, and you have to define the mapping from logical database names to driver type, host, username etc. in a setup dialog).		Make sure that ODBC has been installed and configured on your machine, when using ODBC actions (on most machines, this is already installed, and you have to define the mapping from logical database names to driver type, host, username etc. in a setup dialog). This is operating system specific and out of the scope of the expecco documentation. Please consult your administrator on how to setup the ODBC configuration.

	== Connecting / Disconnecting ==		== Connecting / Disconnecting ==

Cg: /* SQL Queries */

2019-10-17T21:18:57Z

SQL Queries

← Nächstältere Version		Version vom 17. Oktober 2019, 21:18 Uhr
Zeile 27:		Zeile 27:
	Similar to the above, but the resulting rows are sent individually to the output pin. Thus, for every result, one output table is generated, and the receiving action will be triggered once for each.		Similar to the above, but the resulting rows are sent individually to the output pin. Thus, for every result, one output table is generated, and the receiving action will be triggered once for each.

			<hr>
	{{noprint\| 1=		{{noprint\| 1=
	Back to [[Online Documentation#Library_and_Plugin_Overview\|Online Documentation]]		Back to [[Online Documentation#Library_and_Plugin_Overview\|Online Documentation]]

Cg am 17. Oktober 2019 um 21:18 Uhr

2019-10-17T21:18:38Z

← Nächstältere Version		Version vom 17. Oktober 2019, 21:18 Uhr
Zeile 5:		Zeile 5:

	Make sure that ODBC has been installed and configured on your machine, when using ODBC actions (on most machines, this is already installed, and you have to define the mapping from logical database names to driver type, host, username etc. in a setup dialog).		Make sure that ODBC has been installed and configured on your machine, when using ODBC actions (on most machines, this is already installed, and you have to define the mapping from logical database names to driver type, host, username etc. in a setup dialog).

⚫	{{noprint\| 1=
⚫	Back to [[Online Documentation#Library_and_Plugin_Overview\|Online Documentation]]
⚫	}}

	== Connecting / Disconnecting ==		== Connecting / Disconnecting ==
Zeile 30:		Zeile 26:

	Similar to the above, but the resulting rows are sent individually to the output pin. Thus, for every result, one output table is generated, and the receiving action will be triggered once for each.		Similar to the above, but the resulting rows are sent individually to the output pin. Thus, for every result, one output table is generated, and the receiving action will be triggered once for each.

		⚫	{{noprint\| 1=
		⚫	Back to [[Online Documentation#Library_and_Plugin_Overview\|Online Documentation]]
		⚫	}}