MariaDB SQL Table Update

Provides an efficient way for executing bulk insert/update on a MariaDB database without having to hand-write INSERT or UPDATE statements.

This Node may be affected by Windows Regional Settings.

Revision History

1.0.0.0 Initial release

Properties

Connection

Type: Connection Input

Server
Type: String
The name or IP address of the server hosting the MariaDB server instance. Specify a DropPoint if you need to access an instance that is not publically exposed.

Database
Type: String
The name of the database to connect to.

UserName
Type: String
The username to be used for the connection

Password
Type: Password
The password to be used for the connection

DatabasePort
Type: Number
The port on which the MariaDB server is running

UseSsl
Type: Boolean
Whether SSL should be used when making a connecting to the database

Schema

Type: [String
The name of the schema you want to affect with your update.

Table

Type: Json Input
A JSON representation of the data to be updated or inserted (see Remarks)

KeyFields

Type: String Input
A comma-separated list of fields that represent key fields for the update or insert operation. These values will be matched in the target table to determine whether the row already exists. The key fields listed in this property must be supplied in the Table property. It is not necessary to supply key fields if AllowUpdate is false.

AllowInsert

Type: Boolean Input
Indicates whether inserts are allowed into the target table.

AllowUpdate

Type: Boolean Input
Indicates whether updates are allowed into the target table (requires at least one field to be specified in KeyFields).

RowsAffected

Type: Int32 Output
Returns the number of rows affected by the insert/update operation.

Remarks

The JSON supplied should look like the following:

{
	"TableName": [
		{
			"code": "123",
			"description": "first item",
			"amount": 100
		},
		{
			"code": "456",
			"description": "second item",
			"amount": 85
		}
	]
}

When AllowUpdate is true, the fields specified in KeyFields will be matched from TableXml to the target table. All KeyFields supplied must exist in both TableXml and the target table. Multiple key fields should be separated with commas. Note that the specified KeyFields do not have to be the database primary key fields but should indicate the key fields for purposes of the update operation.

For example, if an inventory table contains the fields id (int), code (varchar(50)), description (varchar(100)), the KeyFields property could be set to code if it was necessary to update based on this value rather than the internal integer id field.

If you need to integrate with a non-Microsoft SQL database, refer to Integrating with SQL Databases for additional information and connection strings.

When a column is an identity column, and specific values needs to be inserted, a custom field 'IdentityInsert' with value 'true' could be added to the node.

For tables and columns with spaces, the xml tag name will have to be escaped to make it valid xml. A space should be escaped as _0x0020_

A full list of characters can be found here: Unicode UCS-2 Code Chart (columbia.edu)

Troubleshooting

The most common error that occurs is "Failed to convert parameter value from a String to a Double" (or other numeric type). This occurs due to the Regional Settings in place on the machine on which the DropPoint is running. For example, if the decimal separator is set to a comma, only numbers containing a comma decimal separator will be parsed correctly.

To resolve these problems, first determine exactly which field or fields are not being converted correctly by progressively reducing your JSON payload until it contains only the problem fields. Next, review the regional settings at the DropPoint.

If it is not possible to change Regional Settings on the machine, the numeric fields need to be formatted in a way that conforms to the Regional Settings.