SQL Update statement
- FlowHeater-Team
- Topic Author
- Offline
- Admin
Less
More
13 years 3 weeks ago - 4 months 6 days ago #2089
by FlowHeater-Team
Best wishes
Robert Stark
Did this answer your question? We would be grateful if you provide a brief comment as feedback. It may also help others who may have encountered a similar problem.
SQL Update statement was created by FlowHeater-Team
Translated submission in the German forum. You can read the original entry
here
.
Hello,
I want to update a field of an SQL database, in this case overwriting a value of 9 to 0 (the record is to be cleared).
Should I place the SQL Adapter on both READ and WRITE sides with the relevant database table?
Is the field then updated using a Replace Heater?
I have experimented with it this way and obtain the following SQL statement:
update [VEIS_INVOICE] set [ENTITYSTATE] = 0 where [PK_VEIS_INVOICE] = null
But it doesn’t work.
What am I doing wrong?
Best wishes
Martin
Hello,
I want to update a field of an SQL database, in this case overwriting a value of 9 to 0 (the record is to be cleared).
Should I place the SQL Adapter on both READ and WRITE sides with the relevant database table?
Is the field then updated using a Replace Heater?
I have experimented with it this way and obtain the following SQL statement:
update [VEIS_INVOICE] set [ENTITYSTATE] = 0 where [PK_VEIS_INVOICE] = null
But it doesn’t work.
What am I doing wrong?
Best wishes
Martin
Best wishes
Robert Stark
Did this answer your question? We would be grateful if you provide a brief comment as feedback. It may also help others who may have encountered a similar problem.
Last edit: 4 months 6 days ago by FlowHeater-Team.
Please Log in to join the conversation.
- FlowHeater-Team
- Topic Author
- Offline
- Admin
13 years 3 weeks ago #2090
by FlowHeater-Team
Best wishes
Robert Stark
Did this answer your question? We would be grateful if you provide a brief comment as feedback. It may also help others who may have encountered a similar problem.
Replied by FlowHeater-Team on topic Re:SQL Update statement
Hallo Martin,
Your approach of using the same table twice (once for READ, once for WRITE) is correct.
In order that an SQL Update statement is (correctly) generated, the Primary Key fields of the READ/WRITE sides must be connected together.
All of the Heaters connected are always executed and this also applies to an UPDATE.
Please make certain that in the Configurator for the SQL Server Adapter on the WRITE side that the option UPDATE is checked! Then everything should work.
WARNING: If on the READ side you do not define a WHERE clause restriction, then all records in the table are updated.
Your approach of using the same table twice (once for READ, once for WRITE) is correct.
In order that an SQL Update statement is (correctly) generated, the Primary Key fields of the READ/WRITE sides must be connected together.
All of the Heaters connected are always executed and this also applies to an UPDATE.
Please make certain that in the Configurator for the SQL Server Adapter on the WRITE side that the option UPDATE is checked! Then everything should work.
WARNING: If on the READ side you do not define a WHERE clause restriction, then all records in the table are updated.
Best wishes
Robert Stark
Did this answer your question? We would be grateful if you provide a brief comment as feedback. It may also help others who may have encountered a similar problem.
Please Log in to join the conversation.
Time to create page: 0.260 seconds