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: > > Quoting Brandon Goodin <[EMAIL PROTECTED]>: > > > > <snip> > > > in the road map. I didn't want to steal roberto's thunder and figured > > > he'd spin off with a thread about prioritizing the roadmap. If we'd > > > rather talk about it in this thread that is fine. But, i think it > > > would get more specific attention in another thread. > > > > LOL! Ask and ye shall receive... > > > > 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) > > > > Roberto > > > > >
