[#804] - Separate iReportConnection definitions from config.xml

Issue moved from:
https://sourceforge.net/tracker/index.php?func=detail&aid=1427292&group_...

Consult the original issue for any attachments.

[ 1427292 ] Separate iReportConnection definitions from config.xml

Submitted By: tortois - tortois
Date Submitted: 2006-02-08 02:02
Last Updated By: tortois - Comment added
Date Last Updated: 2006-02-10 02:28
Number of Comments: 2
Number of Attachments: 0
Group: Next Release
Assigned To: Giulio Toffoli
Priority: 5

Summary:
Separate iReportConnection definitions from config.xml The process of defining and modifying new data sources can be quite long and even longer if you have many
instances of the database to test a report against...

In addition if there are several people working on the same datasources it must be repeated x-times since datasource definitions are stored individually for each user.

<iReportConnection> tag in config.xml is basically not a user preference but rather setting (that can be shared among many users).

Why not separate iReportConnections from config.xml and place it in additional external file (datasources.xml perhaps)? It would be useful is this file could be pointed somewhere under options. This way user would get ability to switch datasources
using external file without need for editing config.xml.

Comments

Date: 2006-02-10 02:28
Sender: tortois
Logged In: YES
user_id=1446815

Import/export buttons sound good.

Will they support export of the selected items in the list? I've noticed there can be many connections/datasources with the same name. Won't this present problems while importing items to the list?

Date: 2006-02-08 09:59
Sender: gt78SourceForge.net SubscriberProject Admin
Logged In: YES
user_id=616744

What about export/import buttons in the connections window?
Different users could have different profiles for
accessing the database...

Giulio

No Files Currently Attached