Upsert #5
Upsert #5
Conversation
Update unittest UpsertRowByPrimaryKeyMSSQLSpec
from gitignore
Add limitation in Readme
2. Updated actions DeleteRowByPrimaryKey and LookupRowByPrimaryKey 3. Add unittest for Delete action
…and common for all types of DB
Refactor query
README.md
Outdated
| Before you can deploy any code into elastic.io **you must be a registered elastic.io platform user**. Please see our home page at [http://www.elastic.io](http://www.elastic.io) to learn how. | ||
| #### Environment variables | ||
| For unit-testing | ||
| For unit-testing is needed specify following environment variables: |
There was a problem hiding this comment.
For unit-testing is needed to specify following environment variables
README.md
Outdated
| As an input metadata you will get a Primary Key field to provide the data inside as a clause value. | ||
|
|
||
| ## Current limitations | ||
| 1. Only tables with one [PRIMARY KEY](https://en.wikipedia.org/wiki/Primary_key "PRIMARY KEY") is supported. Message ``Table has not Primary Key. Should be one Primary Key |
There was a problem hiding this comment.
Only tables with one PRIMARY KEY is supported.
You will see the message Table has not Primary Key. Should be one Primary Key, if the selected table doesn't have a primary key. Also, you will see the message Composite Primary Key is not supported, if the selected table has composite primary key.
README.md
Outdated
| 1. Only tables with one [PRIMARY KEY](https://en.wikipedia.org/wiki/Primary_key "PRIMARY KEY") is supported. Message ``Table has not Primary Key. Should be one Primary Key | ||
| `` should be displayed if the table without any primary key will be selected and message ``Composite Primary Key is not supported | ||
| `` should be displayed if the table with composite primary key will be selected. | ||
| 2. Only following versions of DataBase are supported: |
There was a problem hiding this comment.
Only following versions of database types are supported:
README.md
Outdated
| - ``PostgreSQL`` - compatible with PostgreSQL 8.2 and higher | ||
| - ``Oracle`` - compatible with Oracle Database 8.1.7 - 12.1.0.2 | ||
| - ``MSSQL`` - compatible with Microsoft SQL Server 2008 R2 and higher | ||
| 3. For Action "Upsert by primary key" metadata analysis ignores nullable/non-nullable fields, it will be throw SQL Server exception ``Cannot insert the value NULL into...`` if non-nullable fields don't fill for Insert operation. |
There was a problem hiding this comment.
The current implementation of the action Upsert By Primary Key doesn't mark non-nullable fields as required fields at a dynamic metadata. In case of updating such fields with an empty value you will get SQL Exception Cannot insert the value NULL into.... You should manually fill in all non-nullable fields with previous data, if you want to update part of columns in a row, even if data in that fields doesn't change.
src/test/groovy/io/elastic/jdbc/actions/delete/DeleteActionMSSQLSpec.groovy
Show resolved
Hide resolved
src/test/groovy/io/elastic/jdbc/actions/delete/DeleteActionMySQLSpec.groovy
Show resolved
Hide resolved
src/test/groovy/io/elastic/jdbc/actions/delete/DeleteActionOracleSpec.groovy
Show resolved
Hide resolved
src/test/groovy/io/elastic/jdbc/actions/delete/DeleteActionPostrgeSpec.groovy
Show resolved
Hide resolved
src/test/groovy/io/elastic/jdbc/actions/upsert/UpsertRowByPrimaryKeyMSSQLSpec.groovy
Show resolved
Hide resolved
2 participants
No description provided.