We value your feedback.
Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!
Course Of The Month
Become a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Deleting & database triggers
Posted on 1997-12-08
I have a table, with a trigger on it wich prevents certain deletes.
A Delphi program tries to delete a record, but the trigger prevents it from being deleted. However, my delphi progam doesn't show the record anymore, unless i do a refresh. Is there an OTHER way (so without me doing a refresh) to keep on seeing that record ?
A Delphi program tries to delete a record, but the trigger prevents it from being deleted. However, my delphi progam doesn't show the record anymore, unless i do a refresh. Is there an OTHER way (so without me doing a refresh) to keep on seeing that record ?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
3
-
2
- +1
7 Comments
Try adding some type of code into your trigger that forces a refresh when the trigger is triggered.... This way it will automatically refresh.
If this is the type of answer an expert gives, i'm also an expert. How can i get my SQL forcing a refresh of my Delphi Datasource ?
But i'd rather like my Delphi recognize the fact that the record still exists !
Hoping for a real answer !
But i'd rather like my Delphi recognize the fact that the record still exists !
Hoping for a real answer !
(Anyone who can point a browser to this site can probably
register as an expert too...)
Anyway for my real answer:
I do not know that database server you use but normally
your "Delete from ..." SQL will generate some sort of
error message when you execute it. (Although common sense suggests that you should receive an error message whenever the
delete fails...)
You should execute the SQL by hand and see what happens if
the trigger prevents the delete. If there is no error, you
have a problem at the server side (IMHO)
If there is an error, then you can catch that error in your code
and you bnever have to refresh in the first place.
Good Luck,
(And please, please please use the TSQL component,)
register as an expert too...)
Anyway for my real answer:
I do not know that database server you use but normally
your "Delete from ..." SQL will generate some sort of
error message when you execute it. (Although common sense suggests that you should receive an error message whenever the
delete fails...)
You should execute the SQL by hand and see what happens if
the trigger prevents the delete. If there is no error, you
have a problem at the server side (IMHO)
If there is an error, then you can catch that error in your code
and you bnever have to refresh in the first place.
Good Luck,
(And please, please please use the TSQL component,)
Isn't TSQL part of oracle ? I use M$ $QL$ERVER !
if a trigger does a rollback of the transaction, there is no real error occuring. It's just part of the business rules, that you can't delete a specific record. In MS SQLServer, Stored procedures can return a kind of status level, but triggers cannot. So i keep on looking for a solution ...
if a trigger does a rollback of the transaction, there is no real error occuring. It's just part of the business rules, that you can't delete a specific record. In MS SQLServer, Stored procedures can return a kind of status level, but triggers cannot. So i keep on looking for a solution ...
Jeez... almost to simple to warrant an answer, but here goes anyway...
If the trigger causes a rollback (failed delete) then INSIDE the trigger issue a RAISERROR statement that you can capture with Delphi to indicate that yes, the delete was *attempted* but it failed due to a business rule conflict. When you issue the RAISEERROR statement try and use an error code that is not normally in use by MS SQL Server but is meaningful in the context of your application/business rules.
When Delphi recieves anything other than a successful completion code (0) back from the server it assumes there was a failure of that operation (be it Update, Delete or Insert) and WILL NOT remove that record from the result set on the client side.
The apps I'm working with do this on a regular basis, it's part of standard SQL knowledge in regard to client/server architecture :P
Good luck with your project
Pegasus
If the trigger causes a rollback (failed delete) then INSIDE the trigger issue a RAISERROR statement that you can capture with Delphi to indicate that yes, the delete was *attempted* but it failed due to a business rule conflict. When you issue the RAISEERROR statement try and use an error code that is not normally in use by MS SQL Server but is meaningful in the context of your application/business rules.
When Delphi recieves anything other than a successful completion code (0) back from the server it assumes there was a failure of that operation (be it Update, Delete or Insert) and WILL NOT remove that record from the result set on the client side.
The apps I'm working with do this on a regular basis, it's part of standard SQL knowledge in regard to client/server architecture :P
Good luck with your project
Pegasus
Featured Post
![[Live Webinar] The Cloud Skills Gap](https://filedb.experts-exchange.com/files/public/2017/5/29/3249c5dc-214e-4f8f-afab-ef354630e19f.png)
As Cloud technologies come of age, business leaders grapple with the impact it has on their team's skills and the gap associated with the use of a cloud platform.
Join experts from 451 Research and Concerto Cloud Services on July 27th where we will examine fact and fiction.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Introduction
The parallel port is a very commonly known port, it was widely used to connect a printer to the PC, if you look at the back of your computer, for those who don't have newer computers, there will be a port with 25 pins and a small print…
Hello everybody
This Article will show you how to validate number with TEdit control,
What's the TEdit control?
TEdit is a standard Windows edit control on a form, it allows to user to write, read and copy/paste single line of text.
Usua…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month7 days, 6 hours left to enroll
Earn Certification
CompTIA IT Fundamentals
$49.00$44.10
623 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.