|
Next Release
Ok folks,
I'd like to plan the next release of iBatis and would like to know "What do you want?" I would like to make a few small releases to bridge the 1.X line & the existing 3.X line due to the number of breaking changes in the 3.X line. Some things I want to do for 'just me' are:
1. Feature match the Java version
2. Fix an annoying list non lazy load bug
3. Rev to my Castle.DynamicProxy2 patch
4. Expose a QueryForDataTable
5. Drop .net 1.X compatibility.
6. Lastly, I would like something ambitious like Orin's Binsor for Castle on the configuration front.
--
Michael
|
|
Re: Next Release
First... Welcome Michael! I'm excited to have some fresh blood on the project. Sounds like you are ready to jump in.
Are you planning on making changes to the 1.x line, or are you planning all this work in the 3.x line? Is your goal backward compatibility or a 1.x release marking breaks as deprecated?
Do you have list of Java features you are suggesting?
My list: Upgrade to nUnit 2.5 (breaking changes) Include nUnit in externals-bin and reference it there so we control what version is used and it is consistent
Allow for a nullable column(s) check to see if an object is even created for N+1 selects Allow for a column prefix when defining groupBy and resultMap so you can reuse resultMaps
Mike
On Mon, Jun 22, 2009 at 8:28 AM, Michael McCurrey <mmccurrey@...> wrote:
Ok folks,
I'd like to plan the next release of iBatis and would like to know "What do you want?" I would like to make a few small releases to bridge the 1.X line & the existing 3.X line due to the number of breaking changes in the 3.X line. Some things I want to do for 'just me' are:
1. Feature match the Java version
2. Fix an annoying list non lazy load bug
3. Rev to my Castle.DynamicProxy2 patch
4. Expose a QueryForDataTable
5. Drop .net 1.X compatibility.
6. Lastly, I would like something ambitious like Orin's Binsor for Castle on the configuration front.
--
Michael
|
|
Re: Next Release
I would like to first make changes to the 1.X line so as to 'air it out' and make it current for those using it on the 3.X line of .net as well as to solidify 3.X What I'd like to avoid with iBatis is a one time 'big hit'.
I don't have a java feature list yet, I planned on doing it this week. I like *all* of your suggestions, and would like to include them. One feature most folks don't know about is that you can use anonymous types for both results & parameter classes... This should be documented.
On Mon, Jun 22, 2009 at 7:58 AM, Michael Schall <mike.schall@...> wrote:
First... Welcome Michael! I'm excited to have some fresh blood on the project. Sounds like you are ready to jump in.
Are you planning on making changes to the 1.x line, or are you planning all this work in the 3.x line? Is your goal backward compatibility or a 1.x release marking breaks as deprecated?
Do you have list of Java features you are suggesting?
My list: Upgrade to nUnit 2.5 (breaking changes) Include nUnit in externals-bin and reference it there so we control what version is used and it is consistent
Allow for a nullable column(s) check to see if an object is even created for N+1 selects Allow for a column prefix when defining groupBy and resultMap so you can reuse resultMaps
Mike
On Mon, Jun 22, 2009 at 8:28 AM, Michael McCurrey <mmccurrey@...> wrote:
Ok folks,
I'd like to plan the next release of iBatis and would like to know "What do you want?" I would like to make a few small releases to bridge the 1.X line & the existing 3.X line due to the number of breaking changes in the 3.X line. Some things I want to do for 'just me' are:
1. Feature match the Java version
2. Fix an annoying list non lazy load bug
3. Rev to my Castle.DynamicProxy2 patch
4. Expose a QueryForDataTable
5. Drop .net 1.X compatibility.
6. Lastly, I would like something ambitious like Orin's Binsor for Castle on the configuration front.
--
Michael
-- Michael J. McCurrey Read with me at http://www.mccurrey.comhttp://chaoticmindramblings.blogspot.com/
|
|
 Re: Next Release
I like this idea. I run into this problem quite often myself. A Binsor typish port wouldn't solve this, but this wouldn't be hard to do via a build-event check. On Mon, Jun 22, 2009 at 7:16 AM, Tom Kise <TOKI@...> wrote:
Hi Michael
We have a wish for compile time check against type safety, as
IBatis today will fail runtime only, if there is an error in the XML-files. It could
be that is what you want to have a look at regarding number 6 on your list, but
I’m not sure?
Best regards
TOM KISE ://
MANAGER /
DEVELOPMENT 1 /
--------------------------------------------
EMENTOR DANMARK A/S ://
LAUTRUPVANG 12 /
DK-2750 BALLERUP /
T :// +45 70 222 770 /
M :// +45 72 208 194 /
F :// +45 70 222 768 /
MAIL :// tom.kise@.../
EMENTOR.DK
Ok folks,
I'd like to plan the next release of iBatis and would like to know "What
do you want?" I would like to make a few small releases to
bridge the 1.X line & the existing 3.X line due to the number of breaking
changes in the 3.X line. Some things I want to do for 'just me' are:
1. Feature match the Java version
2. Fix an annoying list non lazy load bug
3. Rev to my Castle.DynamicProxy2 patch
4. Expose a QueryForDataTable
5. Drop .net 1.X compatibility.
6. Lastly, I would like something ambitious like Orin's Binsor for Castle
on the configuration front.
--
Michael
-- Michael J. McCurrey Read with me at http://www.mccurrey.comhttp://chaoticmindramblings.blogspot.com/
|
|
Re: Next Release
Hi Michael,
is nice to see someone had continues IBatis.NET development. Congratulations. And what I want for next release is enough to had IBatis.NET features as same as Java.
Thank you.
ucin
--- Pada Sen, 22/6/09, Michael McCurrey < mmccurrey@...> menulis:
> Dari: Michael McCurrey < mmccurrey@...>
> Topik: Re: Next Release
> Kepada: "Tom Kise" < TOKI@...>
> Cc: user-cs@...
> Tanggal: Senin, 22 Juni, 2009, 10:13 PM
> I like this idea. I run into this
> problem quite often myself. A Binsor typish port
> wouldn't solve this, but this wouldn't be hard to do
> via a build-event check.
>
> On Mon, Jun 22, 2009 at 7:16 AM,
> Tom Kise < TOKI@...>
> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi
> Michael
>
>
>
> We
> have a wish for compile time check against type safety, as
> IBatis today will fail runtime only, if there is an error
> in the XML-files. It could
> be that is what you want to have a look at regarding number
> 6 on your list, but
> I’m not sure?
>
>
>
> Best regards
>
>
>
> TOM KISE ://
>
> MANAGER /
>
> DEVELOPMENT 1 /
>
>
>
> --------------------------------------------
>
>
>
> EMENTOR DANMARK A/S ://
>
> LAUTRUPVANG 12 /
>
> DK-2750 BALLERUP /
>
> T :// +45 70 222 770 /
>
> M :// +45 72 208 194 /
>
> F :// +45 70 222 768 /
>
> MAIL :// TOM.KISE@... /
>
>
> EMENTOR.DK
>
>
>
>
>
>
>
>
>
>
> From: Michael McCurrey
> [mailto: mmccurrey@...]
>
>
> Sent: 22. juni 2009 15:29
>
> To: user-cs@...
>
> Subject: Next Release
>
>
>
>
>
>
>
> Ok folks,
>
>
>
> I'd like to plan the next release of iBatis and would
> like to know "What
> do you want?" I would like to make a few small
> releases to
> bridge the 1.X line & the existing 3.X line due to the
> number of breaking
> changes in the 3.X line. Some things I want to do for
> 'just me' are:
>
>
>
> 1. Feature match the Java version
>
> 2. Fix an annoying list non lazy load bug
>
> 3. Rev to my Castle.DynamicProxy2 patch
>
> 4. Expose a QueryForDataTable
>
> 5. Drop .net 1.X compatibility.
>
> 6. Lastly, I would like something ambitious like
> Orin's Binsor for Castle
> on the configuration front.
>
>
>
>
>
> --
>
> Michael
>
>
>
>
>
>
>
>
>
>
>
> --
> Michael J. McCurrey
> Read with me at http://www.mccurrey.com> http://chaoticmindramblings.blogspot.com/>
>
>
Akses email lebih cepat. Yahoo! menyarankan Anda meng-upgrade browser ke Internet Explorer 8 baru yang dioptimalkan untuk Yahoo! Dapatkan di sini!
http://downloads.yahoo.com/id/internetexplorer
|
|
RE: Next Release
Some parts of this message have been removed.
Learn more about Nabble's security policy.
As others have mentioned, the only thing that I’d really like to
see is a “bug-fixes-only” release of the 1.x branch that finally brings it up
to date with what’s in source control. I don’t mind if 3.x breaks compatibility
and has new features (which it seems it already has) since it is clearly marked
as a major release.
If 1.X maintains compatibility with .NET 1.x, then I think that
it should maintain compatibility through its entire lifetime, and save dropping
the legacy support for the 3.x line, where other things are breaking anyway.
Thanks for your dedication to the project!
V/R,
Nicholas Piasecki
Ok folks,
I'd like to plan the next release of iBatis and would like to know "What
do you want?" I would like to make a few small releases to
bridge the 1.X line & the existing 3.X line due to the number of breaking
changes in the 3.X line. Some things I want to do for 'just me' are:
1. Feature match the Java version
2. Fix an annoying list non lazy load bug
3. Rev to my Castle.DynamicProxy2 patch
4. Expose a QueryForDataTable
5. Drop .net 1.X compatibility.
6. Lastly, I would like something ambitious like Orin's Binsor for Castle
on the configuration front.
--
Michael
|
|
Re: Next Release
For me: 1) for 1.6.2 beta, I'd like to see a GA version with JIRA checked if there's any bug for it. 2) an new version with 1.6.x with QueryForDataTable, Castle.DynamicProxy2 is a bouns but not a must.
3) I don't mind the breaking changes currently in V3. ISqlMapper is designed to be singleton-per-thread in 1.6.x, the 3.x code in repository addresses this issue and provides a more flexible connection management model. It will be better to keep these broken changes and I think it is easy to add a wrapper that acts as ISqlMapper in 1.6.x.
4) I think the IMapperFactory interface in V3 can be discarded for some reasons: a) to keep the simplicity of iBATIS.NET b) Visual Studio provides powerful DSL tools. IMapperFactory can be easily complished with generative programming by user rather than in iBATIS.NET.
5) NUnit 2.5 enables generic test, it will simplifies writing tests for testing iBATIS on different database. Yaojian On Mon, Jun 22, 2009 at 9:28 PM, Michael McCurrey <mmccurrey@...> wrote:
Ok folks,
I'd like to plan the next release of iBatis and would like to know "What do you want?" I would like to make a few small releases to bridge the 1.X line & the existing 3.X line due to the number of breaking changes in the 3.X line. Some things I want to do for 'just me' are:
1. Feature match the Java version
2. Fix an annoying list non lazy load bug
3. Rev to my Castle.DynamicProxy2 patch
4. Expose a QueryForDataTable
5. Drop .net 1.X compatibility.
6. Lastly, I would like something ambitious like Orin's Binsor for Castle on the configuration front.
--
Michael
|
|
Re: Next Release
Some parts of this message have been removed.
Learn more about Nabble's security policy.
Do we need to focus on the V1 line still?
QueryForDataTable is already in V3. V3 has support for alternative config processors (SqlMap.config.json). .NET 1.1 has already been dropped in V3. It seems like an awful lot of work on a version that is going away.
From: Michael McCurrey <mmccurrey@...>
To: user-cs@...
Sent: Monday, June 22, 2009 9:28:48 AM
Subject: Next Release
Ok folks, I'd like to plan the next release of iBatis and would like to know "What do you want?" I would like to make a few small releases to bridge the 1.X line & the existing 3.X line due to the number of breaking changes in the 3.X line. Some things I want to do for 'just me' are:
1. Feature match the Java version 2. Fix an annoying list non lazy load bug 3. Rev to my Castle.DynamicProxy2 patch 4. Expose a QueryForDataTable 5. Drop .net 1.X compatibility. 6. Lastly, I would like something ambitious like Orin's Binsor for Castle on the configuration front.
-- Michael
|
|
RE: Next Release
Some parts of this message have been removed.
Learn more about Nabble's security policy.
BTW, my company and I depend heavily on iBatis.NET thanks for your
efforts.
Regarding new release features, any plans to support nested
transactions?
Thanks,
Rafi
Ok folks,
I'd like to plan the next release of iBatis and would like to know "What
do you want?" I would like to make a few small releases to
bridge the 1.X line & the existing 3.X line due to the number of breaking
changes in the 3.X line. Some things I want to do for 'just me' are:
1. Feature match the Java version
2. Fix an annoying list non lazy load bug
3. Rev to my Castle.DynamicProxy2 patch
4. Expose a QueryForDataTable
5. Drop .net 1.X compatibility.
6. Lastly, I would like something ambitious like Orin's Binsor for Castle
on the configuration front.
--
Michael
|
|
Re: Next Release
It can be looked at, however, I would recommend looking at the Castle facility for iBatis. It provides you with this functionality 'today'. On Wed, Jun 24, 2009 at 9:52 AM, Rafi Ghazarian <rghazarian@...> wrote:
BTW, my company and I depend heavily on iBatis.NET thanks for your
efforts.
Regarding new release features, any plans to support nested
transactions?
Thanks,
Rafi
From: Michael McCurrey
[mailto:mmccurrey@...]
Sent: Monday, June 22, 2009 6:29 AM
Ok folks,
I'd like to plan the next release of iBatis and would like to know "What
do you want?" I would like to make a few small releases to
bridge the 1.X line & the existing 3.X line due to the number of breaking
changes in the 3.X line. Some things I want to do for 'just me' are:
1. Feature match the Java version
2. Fix an annoying list non lazy load bug
3. Rev to my Castle.DynamicProxy2 patch
4. Expose a QueryForDataTable
5. Drop .net 1.X compatibility.
6. Lastly, I would like something ambitious like Orin's Binsor for Castle
on the configuration front.
--
Michael
-- Michael J. McCurrey Read with me at http://www.mccurrey.comhttp://chaoticmindramblings.blogspot.com/
|
|
RE: Next Release
Some parts of this message have been removed.
Learn more about Nabble's security policy.
Wasn’t aware of that. I will look into that first.
Thank,
Rafi
From: Michael McCurrey
[mailto:mmccurrey@...]
Sent: Wednesday, June 24, 2009 10:04 AM
To: user-cs@...
Subject: Re: Next Release
It can be looked at, however, I
would recommend looking at the Castle facility for iBatis. It provides
you with this functionality 'today'.
On Wed, Jun 24, 2009 at 9:52 AM, Rafi Ghazarian <rghazarian@...>
wrote:
BTW, my company and I depend
heavily on iBatis.NET thanks for your efforts.
Regarding new release features,
any plans to support nested transactions?
Thanks,
Rafi
From: Michael McCurrey [mailto:mmccurrey@...]
Sent: Monday, June 22, 2009 6:29 AM
Ok folks,
I'd like to plan the next release of iBatis and would like to know "What
do you want?" I would like to make a few small releases to
bridge the 1.X line & the existing 3.X line due to the number of breaking
changes in the 3.X line. Some things I want to do for 'just me' are:
1. Feature match the Java version
2. Fix an annoying list non lazy load bug
3. Rev to my Castle.DynamicProxy2 patch
4. Expose a QueryForDataTable
5. Drop .net 1.X compatibility.
6. Lastly, I would like something ambitious like Orin's Binsor for Castle
on the configuration front.
--
Michael
--
Michael J. McCurrey
Read with me at http://www.mccurrey.com
http://chaoticmindramblings.blogspot.com/
|
|
RE: Next Release
Some parts of this message have been removed.
Learn more about Nabble's security policy.
How can I unsubscribe me from receive emails?
Wasn’t aware of that. I will look into that first.
Thank,
Rafi
From: Michael McCurrey
[mailto:mmccurrey@...]
Sent: Wednesday, June 24, 2009 10:04 AM
To: user-cs@...
Subject: Re: Next Release
It can be
looked at, however, I would recommend looking at the Castle facility for
iBatis. It provides you with this functionality 'today'.
On Wed, Jun 24, 2009 at 9:52 AM, Rafi
Ghazarian <rghazarian@...>
wrote:
BTW, my company and
I depend heavily on iBatis.NET thanks for your efforts.
Regarding new
release features, any plans to support nested transactions?
Thanks,
Rafi
From: Michael McCurrey [mailto:mmccurrey@...]
Sent: Monday, June 22, 2009 6:29 AM
Ok folks,
I'd like to plan the next release of iBatis and would like to know "What
do you want?" I would like to make a few small releases to
bridge the 1.X line & the existing 3.X line due to the number of breaking
changes in the 3.X line. Some things I want to do for 'just me' are:
1. Feature match the Java version
2. Fix an annoying list non lazy load bug
3. Rev to my Castle.DynamicProxy2 patch
4. Expose a QueryForDataTable
5. Drop .net 1.X compatibility.
6. Lastly, I would like something ambitious like Orin's Binsor for Castle
on the configuration front.
--
Michael
--
Michael J. McCurrey
Read with me at http://www.mccurrey.com
http://chaoticmindramblings.blogspot.com/
|
|
Re: Next Release
Have been using iBatis.net in our project for a year or so. Definitely glad to see QueryForDataTable in 3.X. as we have written our own wrapper to expose that functionality. Another nice to have would be a similar QueryForXml which is just a variation of the
QueryForDataTable. On Mon, Jun 22, 2009 at 8:28 AM, Michael McCurrey <mmccurrey@...> wrote:
Ok folks,
I'd like to plan the next release of iBatis and would like to know "What do you want?" I would like to make a few small releases to bridge the 1.X line & the existing 3.X line due to the number of breaking changes in the 3.X line. Some things I want to do for 'just me' are:
1. Feature match the Java version
2. Fix an annoying list non lazy load bug
3. Rev to my Castle.DynamicProxy2 patch
4. Expose a QueryForDataTable
5. Drop .net 1.X compatibility.
6. Lastly, I would like something ambitious like Orin's Binsor for Castle on the configuration front.
--
Michael
|
|
Re: Next Release
Some parts of this message have been removed.
Learn more about Nabble's security policy.
The IBatisNetFacility for Castle isn't really being maintained anymore. Its not part of their build. It shouldn't require a lot of effort to freshen it up.
From: Michael McCurrey <mmccurrey@...>
To: user-cs@...
Sent: Wednesday, June 24, 2009 1:04:14 PM
Subject: Re: Next Release
It can be looked at, however, I would recommend looking at the Castle
facility for iBatis. It provides you with this functionality 'today'. On Wed, Jun 24, 2009 at 9:52 AM, Rafi Ghazarian <rghazarian@...> wrote:
BTW, my company and I depend heavily on iBatis.NET thanks for your
efforts.
Regarding new release features, any plans to support nested
transactions?
Thanks,
Rafi
From: Michael McCurrey
[mailto:mmccurrey@...]
Sent: Monday, June 22, 2009 6:29 AM
Ok folks,
I'd like to plan the next release of iBatis and would like to know "What
do you want?" I would like to make a few small releases to
bridge the 1.X line & the existing 3.X line due to the number of breaking
changes in the 3.X line. Some things I want to do for 'just me' are:
1. Feature match the Java version
2. Fix an annoying list non lazy load bug
3. Rev to my Castle.DynamicProxy2 patch
4. Expose a QueryForDataTable
5. Drop .net 1.X compatibility.
6. Lastly, I would like something ambitious like Orin's Binsor for Castle
on the configuration front.
--
Michael
-- Michael J. McCurrey Read with me at http://www.mccurrey.comhttp://chaoticmindramblings.blogspot.com/
|
|
Re: Next Release
Some parts of this message have been removed.
Learn more about Nabble's security policy.
A very basic QueryForDataTable might look like this:
// untested
public static DataTable QueryForDataTable(this ISqlMapper sqlMapper, string statement, object parameter)
{
var dataTableRowDelegate = new QueryWithRowDelegateDataTable();
sqlMapper.QueryWithRowDelegate(statement, parameter, dataTableRowDelegate.RowDelegate);
return dataTableRowDelegate.DataTable;
}
// untested
public class QueryWithRowDelegateDataTable
{
private readonly DataTable _dataTable = new DataTable();
private bool _firstRow = true;
public void RowDelegate(object obj, object parameterObject, IList unused)
{
object[] items = (object[])obj;
if (_firstRow)
{
for (int i = 0; i < items.Length; i++)
{
_dataTable.Columns.Add("DataColumn" + i, items[i].GetType());
}
_firstRow = false;
}
_dataTable.Rows.Add(items);
}
public DataTable DataTable
{
get { return _dataTable; }
}
}
To get the DataTable's column names to match the names of the database column you'd need to hook into MappedStatement.
From: Michael McCurrey <mmccurrey@...>
To: user-cs@...
Sent: Monday, June 22, 2009 9:28:48 AM
Subject: Next Release
Ok folks, I'd like to plan the next release of iBatis and would like to know "What do you want?" I would like to make a few small releases to bridge
the 1.X line & the existing 3.X line due to the number of breaking changes in the 3.X line. Some things I want to do for 'just me' are:
1. Feature match the Java version 2. Fix an annoying list non lazy load bug 3. Rev to my Castle.DynamicProxy2 patch 4. Expose a QueryForDataTable 5. Drop .net 1.X compatibility. 6. Lastly, I would like something ambitious like Orin's Binsor for Castle on the configuration front.
-- Michael
|
|
Re: Next Release
We use it constantly, the 'existing' build actually does compile; it's one of the unit tests that doesn't work. I have it ported to iBatis 3.X; but I don't have it up to their coding style yet and since iBatis 3.X isn't even beta I don't think the Castle group would take it.
On Wed, Jun 24, 2009 at 8:33 PM, Ron Grabowski <rongrabowski@...> wrote:
The IBatisNetFacility for Castle isn't really being maintained anymore. Its not part of their build. It shouldn't require a lot of effort to freshen it up.
From: Michael McCurrey <mmccurrey@...>Sent: Wednesday, June 24, 2009 1:04:14 PM
Subject: Re: Next Release
It can be looked at, however, I would recommend looking at the Castle
facility for iBatis. It provides you with this functionality 'today'. On Wed, Jun 24, 2009 at 9:52 AM, Rafi Ghazarian <rghazarian@...> wrote:
BTW, my company and I depend heavily on iBatis.NET thanks for your
efforts.
Regarding new release features, any plans to support nested
transactions?
Thanks,
Rafi
From: Michael McCurrey
[mailto:mmccurrey@...]
Sent: Monday, June 22, 2009 6:29 AM
Ok folks,
I'd like to plan the next release of iBatis and would like to know "What
do you want?" I would like to make a few small releases to
bridge the 1.X line & the existing 3.X line due to the number of breaking
changes in the 3.X line. Some things I want to do for 'just me' are:
1. Feature match the Java version
2. Fix an annoying list non lazy load bug
3. Rev to my Castle.DynamicProxy2 patch
4. Expose a QueryForDataTable
5. Drop .net 1.X compatibility.
6. Lastly, I would like something ambitious like Orin's Binsor for Castle
on the configuration front.
--
Michael
-- Michael J. McCurrey Read with me at http://www.mccurrey.comhttp://chaoticmindramblings.blogspot.com/
-- Michael J. McCurrey Read with me at http://www.mccurrey.comhttp://chaoticmindramblings.blogspot.com/
|
