4/19/2024 6:32:15 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss SQL Server or Oracle database administration related to SalesLogix databases. View the code of conduct for posting guidelines.
|
|
|
|
SQL Triggers
Posted: 16 Mar 06 9:16 AM
|
abortion pill over the counter where can i buy the abortion pill over the counter read fiogf49gjkf0d Not sure if this is the right forum or not, but here goes 
I seem to recall hearing/reading something somewhere that SLX6.2 supports a form of pseudo-triggers, but can't seem to find any documentation that confirms or denies this... Can anyone point me in the right direction? Muchas gracias!
John |
|
|
|
Re: SQL Triggers
Posted: 16 Mar 06 10:47 AM
|
Well, SLX did release a start of some internals for this, but it never was released and I don't believe that they are even used internally either. According to the devs, the performance was bad and the initial bits never made it past QA.
So for now, there's nothing for SLX triggers 
-Ryan |
|
|
|
Re: SQL Triggers
Posted: 16 Mar 06 11:00 AM
|
amoxicillin without insurance amoxicillin prescription no insurance
There are no user-customizeable triggers implemented in the SalesLogix OLE-DB provider that I know of (but then I'm not on the dev team). Several "pseudo-triggers" are implemented internally by the SalesLogix OLE-DB provider to log TEF files, validate certain data, synchronize table keys, etc. These are not accessible to users for customizations but are the reason why users must always go through the SalesLogix OLE-DB provider.
SalesLogix 7, which of course is not yet released, will have some flexibility with extending the OLE-DB provider. This will include "pseudo-triggers" (intended more for extending security), as well as custom functions. I shouldn't mention anything else until things are finalized, however I have not mentioned anything more about this than what's already public (including the Insights session information, of which security-related topic I will be presenting a short presentation).
- Jon |
|
|
|
Re: SQL Triggers
Posted: 16 Mar 06 11:22 AM
|
Ahh pain of remotes... yeah, that's why I don't use real SQL triggers (as much as I would LOVE to ) Thanks for the quick answers guys!
|
|
|
|
Re: SQL Triggers
Posted: 04 Apr 06 9:18 AM
|
fiogf49gjkf0d If I need to trigger events at the DB level in a system that includes any form of remotes, I tend to populate a queue table with the required information.
Then have a windows service or similar poll this table periodically. If a change has been made, this application will then make the changes using the OLEDB provider.
This has the benefit of making it asynchronous which in turn gets rid of any possible timeout isses on SLX committing the data. Obviously, if the action was to change data on the table originating the change, you have to be careful about getting in a recursive loop.
Now with SQL 2005 it should be even easier with the inclusion of creating queue messages direct from SQL and having your application a queue consumer.
Martin |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|