I have to get it on the wiki...
But anyway, I agree about the one-liner thing...but that could be easily fixed with very simple multiline support in the compiler. In both the C# version and the Ruby version you can do multiline string, for example, in C#:
@"SELECT
FIRST_NAME
LAST_NAME
BIRTH_DATE
FROM PERSON
WHERE LAST_NAME LIKE @lastName
AND DECEASED = false"
Super nice. So annotations can be great, I actually prefer them to XML, as I rarely need to change my SQL without recompiling and running my tests anyway. But I can understand others have different situations --supporting both is fairly straight forward. Luckily, Sun made annotations such just as bad as XML, so it's an easier translation in Java.
The C# Attribute support will be harder to keep consistent with the XML, because there are so many improvements one can make using ordinal parameters and simple things like supporting multiple attributes of the same name clean up the code significantly.
Cheers,
Clinton
On 8/5/06, Larry Meadors <[EMAIL PROTECTED]> wrote:
Heh, my bet is that Sun delivers enough to make iBATIS easier to
write, but still manages to overcomplexificate it enough to make
people still want to use something else.
It is cool to see things like DataSet<Employee> coming from the API,
but unless DataSet extends List, I do not want that anywhere but in my
DAO layer, just like I do not want a ResultSet anywhere but in my DAO
layer. If it does, great! That is a huge advancement.
While stuff like @Select("SELECT * FROM Employee WHERE status = 'A'")
looks very attractive, and simple crud accounts for probably 35-50% of
the statements I use, only about 2% of the SQL I write beyond CRUD
fits into the 1-liner category.
The rest of the SQL statements are those 80-100 line select statements
with dynamic elements...and as much as I like the StringBuilder
class...I still prefer <dynamic> elements to java code. ;-)
So...top question on my list...can/should we use this for iBATIS3? ;-)
Larry
On 8/4/06, Clinton Begin <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I just picked this up from InfoQ. What do you think?
>
>
> =====================
> Blogger Patrick Lightbody noted "I could see JDBC 4.0 replacing my need for
> iBatis" after reading another blog post on JDBC 4.0 functionality. JDBC 4.0
> includes basic O/R mapper functionality that eases the repetitive task of
> copying ResultSet data into objects. It does not handle inheritance or table
> relations however.
> =====================
>
>
> http://www.infoq.com/news/Easier-Database-Development-JDBC
>
> Patrick's a good guy and a respected developer. I appreciate his opinion.
> Obviously, this is only useful for people running JDK 5 or possibly only JDK
> 6. And of course, Annotation support would be an almost brainless effort to
> implement for iBATIS. Your thoughts?
>
> Clinton
>
