I know it is poor form to report two things at once but the replication
instructions are very similar and bugs may be similar.
I am using iBATIS from subversion updated Friday am.
I am interacting with my db solely through stored procedures.
Earlier, I had problems with iBATIS not realizing
Part of the problem is improper syntax for the procedure call. It should
look like this:
procedure id=deleteDatasetByResearcherIdAndIdProcedure
resultClass=Integer parameterClass=Map
{CALL deleteDatasetByResearcherIdAndId(
#pResearcherId:NUMERIC#,
#pDatasetId:NUMERIC#)}
/procedure
Very well said.
On 11/21/06, Peter Andrews [EMAIL PROTECTED] wrote:
Just wanted to say thanks for fixing this. Whenever one finds an issue
in an open source project, it takes time to report it in a useful
manner. Sometimes in the press of getting projects done, if you come up
with a
Since there's nothing in this relase so far that the community is really
wanting/needing, I think it would be worthwhile to take a look at some of
the other open issues before doing another release. Specifically:
1. JIRA 349, 357, 366, and 367 (maybe others too - I haven't done a serious
Just wanted to say thanks for fixing this. Whenever one finds an issue
in an open source project, it takes time to report it in a useful
manner. Sometimes in the press of getting projects done, if you come up
with a workaround for yourself, it is tempting to not bother reporting
it, figuring
I don't want to hold this release up for any non-critical fixes.
The reason I'm putting this up for vote now is that people have been waiting
for this release for a long time. I'd be happy to release 2.3 and then roll
the grouping of JIRA issues you mentioned into 2.4 or 2.3.1, whichever makes
+0
On 11/20/06, Clinton Begin [EMAIL PROTECTED] wrote:
I don't want to hold this release up for any non-critical fixes.
The reason I'm putting this up for vote now is that people have been
waiting for this release for a long time. I'd be happy to release 2.3 and
then roll the grouping of
