Title:
Bug 79564:(Watson Migration Closure)Add support for per-app, code-only volatile datasources that remain private to the app that defines them
| View in TrackerStatus/Resolution/Reason: Closed/Deferred/
Reporter/Name(from Bugbase): David McGuigan / David McGuigan (David McGuigan)
Created: 08/25/2009
Components: Core Runtime, Application
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 /
Priority/Frequency: Normal / Unknown
Locale/System: English / Platforms All
Vote Count: 1
Problem:
Add support for per-app, code-only volatile datasources that remain private to the app that defines them.Meaning they don’t show up in the administrator and aren’t accessible to other applications.Application.cfc: <cfset this.datasource = newDatasource( "MySQL", "ip", "username", "password" {, "port", other options... } ) />This will simplify deployment and make apps more portable as well as provide easier configuration and security for shared hosting.These type of datasources will be volatile, they’ll die with the application and be created on the first serve of each app.If the result is stored in this.datasource instead of an application variable it will also automatically become the default datasource for all queries within this application ( meaning you don’t need to specify one in your query tags unless they use a different ds )
Method:
Result:
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3039759
External Customer Info:
External Company:
External Customer Name: David McGuigan
External Customer Email: 5E0D54C04462BF5E992016B6
External Test Config: 08/25/2009Attachments:
Comments: