tracker issue : CF-3715031

select a category, or use search below
(searches all categories and all time range)
Title:

Adding a new datasource parameter in CFTRANSACTION tag

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/NotABug

Reporter/Name(from Bugbase): Sathish Kumar / Sathish Kumar (Sathish Kumar)

Created: 02/28/2014

Components: Database

Versions: 11.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: PublicBeta /

Priority/Frequency: Trivial / Unknown

Locale/System: English / Platforms All

Vote Count: 0

Hi,

Although there is the new provision to set an application wide datasource using the Application's settings in the Application.cfc since version 10.0, I wonder if it would be good enough to have the ability to set a datasource in the cftransaction tag itself for all queries in a transaction block. There could be many applications that communicates with different datasources and although I do agree that all queries in a transaction block are meant to be executed against a single datasource, I thought it would be much convenient to specify the datasource in the CFTRANSACTION tag itself especially if the action="begin".  I do understand that the CFTRANSACTION tag actually tries to initiate a transaction in the target database and does not do anything else, but it would possibly be easier for Adobe to build the additional feature to implicitly pick the datasource from the CFTRANSACTION tag instead of doing it from the datasource tag of the first query in the transaction block which is what I presume the current CF platform must be doing now.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3715031

External Customer Info:
External Company:  
External Customer Name: Carboncubes.Tech
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments:

Transaction boundaries run across method boundaries and across components. Having a datasource parameter at the transaction tag can cause debugging nightmare. It would be very difficult to figure out which datasource the query is referring to and where it is coming from. Right now, it is very clear that the data source will be defined at the query or in the application. Closing it.
Comment by Rupesh K.
13137 | March 03, 2014 11:48:59 PM GMT