You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ibatis.apache.org by "Roberto Rabe (JIRA)" <ib...@incubator.apache.org> on 2004/12/24 03:12:04 UTC
[jira] Created: (IBATISNET-15) ScriptRunner change to split NUnit Oracle init SQL scripts into multiple commands
ScriptRunner change to split NUnit Oracle init SQL scripts into multiple commands
---------------------------------------------------------------------------------
Key: IBATISNET-15
URL: http://nagoya.apache.org/jira/browse/IBATISNET-15
Project: iBatis for .NET
Type: Improvement
Environment: Latest iBATIS.NET source code from SVN
Reporter: Roberto Rabe
Priority: Minor
Attachments: IBatisNetCommon_Utilities_ScriptRunner.patch
If the changes look ok, I'll start adding the slightly modified Oracle SQL script files into SVN.
Also, this ScriptRunner update will require a change to the InitScript() methods in the tests since RunScript has an additional parameter to indicate if the SQL should be parsed/split into multiple statements or not. Currently, only the InitScript() calls for the various -procedure.sql files need to indicate "false" since the entire SQL source in the file is one statement to execute and doesn't need to be split.
I didn't try to tackle parsing out SQL comments for Oracle (single line with "--" or multi-line with /* */) since this was a pretty quick change to do without attempting to do that (anyway, it's easy enough to just remove the comments from the Oracle SQL script files).
FYI, I'm getting better test results with System.Data.OracleClient than with Oracle.DataAccess/ODP.NET (I haven't finished doing a good job with porting over all of the statements in the SqlMaps though). OleDb for Oracle bombs out on the NUnit tests because the ScriptRunner sees OleDb1.1 as the provider name and doesn't parse the script contents. Oops! ;-)
Roberto
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (IBATISNET-15) ScriptRunner change to split NUnit Oracle init SQL scripts into multiple commands
Posted by "Roberto Rabe (JIRA)" <ib...@incubator.apache.org>.
[ http://nagoya.apache.org/jira/browse/IBATISNET-15?page=history ]
Roberto Rabe updated IBATISNET-15:
----------------------------------
Attachment: IBatisNetCommon_Utilities_ScriptRunner.patch
Uploading ScriptRunner diff/patch.
> ScriptRunner change to split NUnit Oracle init SQL scripts into multiple commands
> ---------------------------------------------------------------------------------
>
> Key: IBATISNET-15
> URL: http://nagoya.apache.org/jira/browse/IBATISNET-15
> Project: iBatis for .NET
> Type: Improvement
> Environment: Latest iBATIS.NET source code from SVN
> Reporter: Roberto Rabe
> Priority: Minor
> Attachments: IBatisNetCommon_Utilities_ScriptRunner.patch
>
> If the changes look ok, I'll start adding the slightly modified Oracle SQL script files into SVN.
> Also, this ScriptRunner update will require a change to the InitScript() methods in the tests since RunScript has an additional parameter to indicate if the SQL should be parsed/split into multiple statements or not. Currently, only the InitScript() calls for the various -procedure.sql files need to indicate "false" since the entire SQL source in the file is one statement to execute and doesn't need to be split.
> I didn't try to tackle parsing out SQL comments for Oracle (single line with "--" or multi-line with /* */) since this was a pretty quick change to do without attempting to do that (anyway, it's easy enough to just remove the comments from the Oracle SQL script files).
> FYI, I'm getting better test results with System.Data.OracleClient than with Oracle.DataAccess/ODP.NET (I haven't finished doing a good job with porting over all of the statements in the SqlMaps though). OleDb for Oracle bombs out on the NUnit tests because the ScriptRunner sees OleDb1.1 as the provider name and doesn't parse the script contents. Oops! ;-)
> Roberto
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (IBATISNET-15) ScriptRunner change to split NUnit Oracle init SQL scripts into multiple commands
Posted by "Gilles Bayon (JIRA)" <ib...@incubator.apache.org>.
[ http://nagoya.apache.org/jira/browse/IBATISNET-15?page=history ]
Gilles Bayon closed IBATISNET-15:
---------------------------------
Resolution: Fixed
Fixed by Roberto
> ScriptRunner change to split NUnit Oracle init SQL scripts into multiple commands
> ---------------------------------------------------------------------------------
>
> Key: IBATISNET-15
> URL: http://nagoya.apache.org/jira/browse/IBATISNET-15
> Project: iBatis for .NET
> Type: Improvement
> Environment: Latest iBATIS.NET source code from SVN
> Reporter: Roberto Rabe
> Priority: Minor
> Attachments: IBatisNetCommon_Utilities_ScriptRunner.patch
>
> If the changes look ok, I'll start adding the slightly modified Oracle SQL script files into SVN.
> Also, this ScriptRunner update will require a change to the InitScript() methods in the tests since RunScript has an additional parameter to indicate if the SQL should be parsed/split into multiple statements or not. Currently, only the InitScript() calls for the various -procedure.sql files need to indicate "false" since the entire SQL source in the file is one statement to execute and doesn't need to be split.
> I didn't try to tackle parsing out SQL comments for Oracle (single line with "--" or multi-line with /* */) since this was a pretty quick change to do without attempting to do that (anyway, it's easy enough to just remove the comments from the Oracle SQL script files).
> FYI, I'm getting better test results with System.Data.OracleClient than with Oracle.DataAccess/ODP.NET (I haven't finished doing a good job with porting over all of the statements in the SqlMaps though). OleDb for Oracle bombs out on the NUnit tests because the ScriptRunner sees OleDb1.1 as the provider name and doesn't parse the script contents. Oops! ;-)
> Roberto
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (IBATISNET-15) ScriptRunner change to split NUnit Oracle init SQL scripts into multiple commands
Posted by "Gilles Bayon (JIRA)" <ib...@incubator.apache.org>.
[ http://nagoya.apache.org/jira/browse/IBATISNET-15?page=comments#action_57032 ]
Gilles Bayon commented on IBATISNET-15:
---------------------------------------
Hy Roberto
Looks fine for me, you could updated in SVN, I will close this issue after.
> ScriptRunner change to split NUnit Oracle init SQL scripts into multiple commands
> ---------------------------------------------------------------------------------
>
> Key: IBATISNET-15
> URL: http://nagoya.apache.org/jira/browse/IBATISNET-15
> Project: iBatis for .NET
> Type: Improvement
> Environment: Latest iBATIS.NET source code from SVN
> Reporter: Roberto Rabe
> Priority: Minor
> Attachments: IBatisNetCommon_Utilities_ScriptRunner.patch
>
> If the changes look ok, I'll start adding the slightly modified Oracle SQL script files into SVN.
> Also, this ScriptRunner update will require a change to the InitScript() methods in the tests since RunScript has an additional parameter to indicate if the SQL should be parsed/split into multiple statements or not. Currently, only the InitScript() calls for the various -procedure.sql files need to indicate "false" since the entire SQL source in the file is one statement to execute and doesn't need to be split.
> I didn't try to tackle parsing out SQL comments for Oracle (single line with "--" or multi-line with /* */) since this was a pretty quick change to do without attempting to do that (anyway, it's easy enough to just remove the comments from the Oracle SQL script files).
> FYI, I'm getting better test results with System.Data.OracleClient than with Oracle.DataAccess/ODP.NET (I haven't finished doing a good job with porting over all of the statements in the SqlMaps though). OleDb for Oracle bombs out on the NUnit tests because the ScriptRunner sees OleDb1.1 as the provider name and doesn't parse the script contents. Oops! ;-)
> Roberto
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira