|Subject:||Document interaction between dsn and other data source attributes during object construction.|
If a data source definition contains both an explicit DSN and attributes that contribute to portions of the DSN, the latter will cause the former to be overwritten. Docpatch attached to clarify that you shouldn't do this.
--- lib/Rose/DB.pm~ 2012-11-24 09:40:01.000000000 -0500 +++ lib/Rose/DB.pm 2013-07-31 11:58:57.000000000 -0400 @@ -3720,6 +3720,8 @@ If the DSN is never set explicitly, it is built automatically based on the relevant object attributes. +If the DSN is set explicitly, but any of L<host|/host>, L<port|/port>, L<database|/database>, L<schema|/schema>, or L<catalog|/catalog> are also provided, either in an object constructor or when the data source is registered, the explicit DSN may be clobbered as an attempt is made to construct a new DSN using these attributes. + =item B<handle_error [VALUE]> Get or set the value of the "HandleError" connect option and L<DBI> handle attribute. If a VALUE is passed, it will be set in both the connect options hash and the current database handle, if any. Returns the value of the "HandleError" attribute of the database handle if it exists, or the connect option otherwise.