>We found that whenever we used transactions, an error would be written to
>our log files, but not thrown to screen. However, if you have the username
>and password set up with the datasource in the cf administrator then you
>wouldn't get any errors.
Thanks for the confirmation on what I'm seeing. However, I'm a bit confused
on your workaround. Are you saying that if you define the user name and
password in the MX Administrator then you don't get the error? If so, that's
not what I'm seeing. I define the user name and password in the MX Admin for
my datasource and still see thing problem. Again though, I may be
misunderstanding what you mean.
>
>We've resorted to doing that for some apps, and moving transactional logic
>to stored procs for others. No fun. But, it's the only solution we've come
>up with so far (Oracle 8i).
Yeah, I've been pushing to move our SQL, particularly the transactional
queries, entirely into Oracle packages. However, I'm a one-man show as far
as CF development at my company, so getting the time to refactor my
inherited code base is slim to none at this point.
Oh well, thanks again for confirming what I'm seeing.
Regards,
Dave.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
