So if dynamic sql is worthy of it's own release. Would it be a 2.2 and then push the current 2.2 to 2.3. Or would we make dynasql a 2.3 release thing after we get the pluggable sql scripting language hooks in place.
Perhaps we move "- Pluggable SQL Scripting languages" into the 2.1 and put dynasql enhancments in 2.3. I'm easy on this subject. I just thought dyna sql would be more of a priority. Brandon On Wed, 2 Feb 2005 13:36:28 -0500, roberto <[EMAIL PROTECTED]> wrote: > > > > Just trying to keep this thread alive (or wake it back up)... > > > > To summarize, here is what it looks like with the given feedback: > > > > ------------------------------------------------------------ > > Road Map > > ------------------------------------------------------------ > > > > 2.1 > > Ease of Use > > - <generate> tag for CRUD methods > > Object Oriented > > - Inheritance via selects or joins (same as groups) > > Flexibility > > - Constructor and field based results (CB: Move up from 2.2?) > > Dynamic SQL > > - Improved syntax/flexibility (BG) > > > > 2.2 > > Ease of Use > > - Improved configuration API and logging > > - Pluggable SQL Scripting languages (RR: related to 2.1 Dynamic SQL?) > > Flexibility > > - Override/extend mapped statements (i.e. reuse SQL; > > overrides="statementName") > > - Constructor and field based results (CB: Move up to 2.1?) > > Performance > > - Cache dependency on other cache (flush-on-dependant) > > - Flush cache at specific time (e.g. 22:30) > > Database Support > > - Save point support > > - Add true autocommit support (mostly for SYBASE procs) > > > > > > Roberto > > > > > > > > > -----Original Message----- > > > From: Brandon Goodin [mailto:[EMAIL PROTECTED] > > > Sent: Saturday, January 29, 2005 10:13 AM > > > To: ibatis-dev@incubator.apache.org; [EMAIL PROTECTED] > > > Subject: Re: Prioritize the iBATIS Java Roadmap > > > > > > I thought we'd work on getting the Ease of Use moved into 2.1. Either > > > that or see "improved dynamic sql" in 2.1. > > > > > > > > > On Sat, 29 Jan 2005 01:53:29 -0700, Clinton Begin > > > <[EMAIL PROTECTED]> wrote: > > > > IMHO, it's already prioritized based on user demand and alignment with > > > > the features already in place in the .NET version. > > > > > > > > A couple from 2.2 may move up...like constructor mapped results. > > > > > > > > Cheers, > > > > Clinton > > > > > > > > On Sat, 29 Jan 2005 01:43:31 -0500, [EMAIL PROTECTED] > > > > <[EMAIL PROTECTED]> wrote: > > > > > Here's the content of road-map.txt: > > > > > > > > > > ------------------------------------------------------------ > > > > > Road Map > > > > > ------------------------------------------------------------ > > > > > > > > > > 2.1 > > > > > Ease of Use > > > > > - <generate> tag for CRUD methods > > > > > Object Oriented > > > > > - Inheritance via selects or joins (same as groups) > > > > > > > > > > 2.2 > > > > > Ease of Use > > > > > - Improved configuration API and logging > > > > > - Pluggable SQL Scripting languages > > > > > Flexibility > > > > > - Override/extend mapped statements (i.e. reuse SQL; > > > > > overrides="statementName") > > > > > - Constructor and field based results > > > > > Performance > > > > > - Cache dependency on other cache (flush-on-dependant) > > > > > - Flush cache at specific time (e.g. 22:30) > > > > > Database Support > > > > > - Save point support > > > > > - Add true autocommit support (mostly for SYBASE procs) > >
