Changes for page SQL Query

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -37,7 +37,7 @@
37	37	* The column names (id, created date, contents)
38	38	* The value per column (:headers[id], :headers[timestamp], :payload)
39	39
40		-When combining all of this you will end up with something like this: INSERT INTO mytable (id, created date, contents) values (:headers[id], :headers[timestamp], :payload). As you can see, we want to insert our row into the table called mytable. We want to insert three values in three separate columns (id, created date, contents). Furthermore, you should note that you can use the header values and (part of) the payload as dynamic input for those values. The notation as depicted above is paramount in making this work.
	40	+When combining all of this you will end up with something like this: {{code language="sql"}}INSERT INTO mytable (id, created date, contents) values (:headers[id], :headers[timestamp], :payload){{/code}}. As you can see, we want to insert our row into the table called mytable. We want to insert three values in three separate columns (id, created date, contents). Furthermore, you should note that you can use the header values and (part of) the payload as dynamic input for those values. The notation as depicted above is paramount in making this work.
41	41
42	42	{{info}}When the primary key value already exists in the database, you will receive an error (duplicate key violation). Just as you would expect when calling a POST twice in a row with the same unique identifier.{{/info}}
43	43