You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ibatis.apache.org by "Ron Grabowski (JIRA)" <ib...@incubator.apache.org> on 2005/05/06 17:34:18 UTC
[jira] Created: (IBATISNET-59) Allow one complete node SqlMap.config
Allow one complete <provider> node SqlMap.config
------------------------------------------------
Key: IBATISNET-59
URL: http://issues.apache.org/jira/browse/IBATISNET-59
Project: iBatis for .NET
Type: New Feature
Versions: DataMapper 1.2
Reporter: Ron Grabowski
Assigned to: Gilles Bayon
Priority: Trivial
Attachments: ParseProvider.cs
This is a follow up to my post on the mailing list:
http://tinyurl.com/cej2y
http://www.mail-archive.com/ibatis-user-cs@incubator.apache.org/msg00352.html
I suspect that many IBatisNet apps are not designed to work against all 10 providers currently in the providers.config file. I think the common case is for an application to run on one or perhaps two databases.
I propose making the providers.config file optional and allowing the user to embed a single <provider> node into the SqlMap.config file:
<database>
<provider
assemblyName="System.Data, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089"
connectionClass="System.Data.OleDb.OleDbConnection"
commandClass="System.Data.OleDb.OleDbCommand"
parameterClass="System.Data.OleDb.OleDbParameter"
parameterDbTypeClass="System.Data.OleDb.OleDbType"
parameterDbTypeProperty="OleDbType"
dataAdapterClass="System.Data.OleDb.OleDbDataAdapter"
commandBuilderClass="System.Data.OleDb.OleDbCommandBuilder"
usePositionalParameters = "true"
useParameterPrefixInSql = "false"
useParameterPrefixInParameter = "false"
parameterPrefix = "" />
<dataSource
name="abc"
connectionString="def"/>
</database>
One of the changes to the source would be to the ParseProvider() method of IBatisNet.DataMapper.Configuration.DomSqlMapBuilder. It would need to know to parse a complete <provider> node if the <provider> had more than just a "name" attribute.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (IBATISNET-59) Allow one complete node SqlMap.config
Posted by "Ron Grabowski (JIRA)" <ib...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/IBATISNET-59?page=all ]
Ron Grabowski updated IBATISNET-59:
-----------------------------------
Attachment: ParseProvider.cs
Example ParseProvider() method that should handle parsing of a complete <provider> node within SqlMap.config.
> Allow one complete <provider> node SqlMap.config
> ------------------------------------------------
>
> Key: IBATISNET-59
> URL: http://issues.apache.org/jira/browse/IBATISNET-59
> Project: iBatis for .NET
> Type: New Feature
> Versions: DataMapper 1.2
> Reporter: Ron Grabowski
> Assignee: Gilles Bayon
> Priority: Trivial
> Attachments: ParseProvider.cs
>
> This is a follow up to my post on the mailing list:
> http://tinyurl.com/cej2y
> http://www.mail-archive.com/ibatis-user-cs@incubator.apache.org/msg00352.html
> I suspect that many IBatisNet apps are not designed to work against all 10 providers currently in the providers.config file. I think the common case is for an application to run on one or perhaps two databases.
> I propose making the providers.config file optional and allowing the user to embed a single <provider> node into the SqlMap.config file:
> <database>
> <provider
> assemblyName="System.Data, Version=1.0.5000.0, Culture=neutral,
> PublicKeyToken=b77a5c561934e089"
> connectionClass="System.Data.OleDb.OleDbConnection"
> commandClass="System.Data.OleDb.OleDbCommand"
> parameterClass="System.Data.OleDb.OleDbParameter"
> parameterDbTypeClass="System.Data.OleDb.OleDbType"
> parameterDbTypeProperty="OleDbType"
> dataAdapterClass="System.Data.OleDb.OleDbDataAdapter"
> commandBuilderClass="System.Data.OleDb.OleDbCommandBuilder"
> usePositionalParameters = "true"
> useParameterPrefixInSql = "false"
> useParameterPrefixInParameter = "false"
> parameterPrefix = "" />
> <dataSource
> name="abc"
> connectionString="def"/>
> </database>
> One of the changes to the source would be to the ParseProvider() method of IBatisNet.DataMapper.Configuration.DomSqlMapBuilder. It would need to know to parse a complete <provider> node if the <provider> had more than just a "name" attribute.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (IBATISNET-59) Allow one complete node SqlMap.config
Posted by "Gilles Bayon (JIRA)" <ib...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/IBATISNET-59?page=all ]
Gilles Bayon closed IBATISNET-59:
---------------------------------
Resolution: Fixed
Fix Version: DataMapper 1.2
> Allow one complete <provider> node SqlMap.config
> ------------------------------------------------
>
> Key: IBATISNET-59
> URL: http://issues.apache.org/jira/browse/IBATISNET-59
> Project: iBatis for .NET
> Type: New Feature
> Versions: DataMapper 1.2
> Reporter: Ron Grabowski
> Assignee: Gilles Bayon
> Priority: Trivial
> Fix For: DataMapper 1.2
> Attachments: ParseProvider.cs
>
> This is a follow up to my post on the mailing list:
> http://tinyurl.com/cej2y
> http://www.mail-archive.com/ibatis-user-cs@incubator.apache.org/msg00352.html
> I suspect that many IBatisNet apps are not designed to work against all 10 providers currently in the providers.config file. I think the common case is for an application to run on one or perhaps two databases.
> I propose making the providers.config file optional and allowing the user to embed a single <provider> node into the SqlMap.config file:
> <database>
> <provider
> assemblyName="System.Data, Version=1.0.5000.0, Culture=neutral,
> PublicKeyToken=b77a5c561934e089"
> connectionClass="System.Data.OleDb.OleDbConnection"
> commandClass="System.Data.OleDb.OleDbCommand"
> parameterClass="System.Data.OleDb.OleDbParameter"
> parameterDbTypeClass="System.Data.OleDb.OleDbType"
> parameterDbTypeProperty="OleDbType"
> dataAdapterClass="System.Data.OleDb.OleDbDataAdapter"
> commandBuilderClass="System.Data.OleDb.OleDbCommandBuilder"
> usePositionalParameters = "true"
> useParameterPrefixInSql = "false"
> useParameterPrefixInParameter = "false"
> parameterPrefix = "" />
> <dataSource
> name="abc"
> connectionString="def"/>
> </database>
> One of the changes to the source would be to the ParseProvider() method of IBatisNet.DataMapper.Configuration.DomSqlMapBuilder. It would need to know to parse a complete <provider> node if the <provider> had more than just a "name" attribute.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (IBATISNET-59) Allow one complete node SqlMap.config
Posted by "Ron Grabowski (JIRA)" <ib...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/IBATISNET-59?page=comments#action_66753 ]
Ron Grabowski commented on IBATISNET-59:
----------------------------------------
This issue can be closed and/or marked as Won't Fix. I agree that embedding providers.config is a good alternative solution and that putting a complete <provider> node in sqlMap.config will clutter the file.
> Allow one complete <provider> node SqlMap.config
> ------------------------------------------------
>
> Key: IBATISNET-59
> URL: http://issues.apache.org/jira/browse/IBATISNET-59
> Project: iBatis for .NET
> Type: New Feature
> Versions: DataMapper 1.2
> Reporter: Ron Grabowski
> Assignee: Gilles Bayon
> Priority: Trivial
> Attachments: ParseProvider.cs
>
> This is a follow up to my post on the mailing list:
> http://tinyurl.com/cej2y
> http://www.mail-archive.com/ibatis-user-cs@incubator.apache.org/msg00352.html
> I suspect that many IBatisNet apps are not designed to work against all 10 providers currently in the providers.config file. I think the common case is for an application to run on one or perhaps two databases.
> I propose making the providers.config file optional and allowing the user to embed a single <provider> node into the SqlMap.config file:
> <database>
> <provider
> assemblyName="System.Data, Version=1.0.5000.0, Culture=neutral,
> PublicKeyToken=b77a5c561934e089"
> connectionClass="System.Data.OleDb.OleDbConnection"
> commandClass="System.Data.OleDb.OleDbCommand"
> parameterClass="System.Data.OleDb.OleDbParameter"
> parameterDbTypeClass="System.Data.OleDb.OleDbType"
> parameterDbTypeProperty="OleDbType"
> dataAdapterClass="System.Data.OleDb.OleDbDataAdapter"
> commandBuilderClass="System.Data.OleDb.OleDbCommandBuilder"
> usePositionalParameters = "true"
> useParameterPrefixInSql = "false"
> useParameterPrefixInParameter = "false"
> parameterPrefix = "" />
> <dataSource
> name="abc"
> connectionString="def"/>
> </database>
> One of the changes to the source would be to the ParseProvider() method of IBatisNet.DataMapper.Configuration.DomSqlMapBuilder. It would need to know to parse a complete <provider> node if the <provider> had more than just a "name" attribute.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (IBATISNET-59) Allow one complete node SqlMap.config
Posted by "Gilles Bayon (JIRA)" <ib...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/IBATISNET-59?page=comments#action_66294 ]
Gilles Bayon commented on IBATISNET-59:
---------------------------------------
The user don't have to know what is in the providers.config and how a provider element is configurated.
He just had to known that he use this named provider.
This solution will complexify the SqlMap.config for nothing.
Rem: now (as in an earlier version) the providers.config can be emebedded or set via an url
> Allow one complete <provider> node SqlMap.config
> ------------------------------------------------
>
> Key: IBATISNET-59
> URL: http://issues.apache.org/jira/browse/IBATISNET-59
> Project: iBatis for .NET
> Type: New Feature
> Versions: DataMapper 1.2
> Reporter: Ron Grabowski
> Assignee: Gilles Bayon
> Priority: Trivial
> Attachments: ParseProvider.cs
>
> This is a follow up to my post on the mailing list:
> http://tinyurl.com/cej2y
> http://www.mail-archive.com/ibatis-user-cs@incubator.apache.org/msg00352.html
> I suspect that many IBatisNet apps are not designed to work against all 10 providers currently in the providers.config file. I think the common case is for an application to run on one or perhaps two databases.
> I propose making the providers.config file optional and allowing the user to embed a single <provider> node into the SqlMap.config file:
> <database>
> <provider
> assemblyName="System.Data, Version=1.0.5000.0, Culture=neutral,
> PublicKeyToken=b77a5c561934e089"
> connectionClass="System.Data.OleDb.OleDbConnection"
> commandClass="System.Data.OleDb.OleDbCommand"
> parameterClass="System.Data.OleDb.OleDbParameter"
> parameterDbTypeClass="System.Data.OleDb.OleDbType"
> parameterDbTypeProperty="OleDbType"
> dataAdapterClass="System.Data.OleDb.OleDbDataAdapter"
> commandBuilderClass="System.Data.OleDb.OleDbCommandBuilder"
> usePositionalParameters = "true"
> useParameterPrefixInSql = "false"
> useParameterPrefixInParameter = "false"
> parameterPrefix = "" />
> <dataSource
> name="abc"
> connectionString="def"/>
> </database>
> One of the changes to the source would be to the ParseProvider() method of IBatisNet.DataMapper.Configuration.DomSqlMapBuilder. It would need to know to parse a complete <provider> node if the <provider> had more than just a "name" attribute.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira