Hi Ayodeji !
I fully agree with you specially if you have few tables and adhere
totally to ORM. But consider what happens when yo have to fill a DataTable
with the result of three+ tables joined, with subselects, group by and
dinamic where clauses...
Would you consider correct to define one Bean-based DataProvider for
each one of such resultsets ?? They are not domain entities, they are just
rows !!
I always had some problems with this side of ORM, sometimes you don't
retrieve a list of entities, sometimes the result is more like a
spreadsheet, and you don't have an easy way of dealing with that based on
beans.
What happens if you call a Stored Procedure and you just don't know how
many columns are returned ?? This is the problem I would like to solve.
Of course I want to do it "the Wicket way", to be able to enjoy all the
benefits already provided by the framework.
I don't want to avoid IDataProvider, I just want to be less tied to the
idea of retrieving beans from the database. This issue troubled me since the
very first time I heard about ORM.
Of course all your concepts regarding the size of the resultset etc. are
completely valid and they must be dealt with.
I'm sorry I haven't had time yet to explore the code you sent me, I'll
see it over the weekend and post it again next week.
Thanks for your help !!
Daniel
Ayodeji Aladejebi wrote:
>
> i think its proper to have a Dataprovider for each table. why i enjoy
> dataprovider in wicket is that it gives me this feeling that SELECT * FROM
> TABLE will not return 1 million records and crash my application, its
> gives
> you a simple way to fetch the data you want to display per time and you
> can
> create a many dataprovider as possible or even implement some internal
> session state logic to tell IDataprovider which table to fetch. its up to
> your implementation.
>
> you will also loose the flexibility you have with yur models if you avoid
> IDataProvider
>
> however actually i think i makes sense for someone to donate a robust
> JDBCDataProvider to wicket stuff
> because attempting to do this for criteria matter, you can only hope you
> are
> not dealing with complex data types
>
>
--
View this message in context:
http://www.nabble.com/Question-regarding-old-post-%28ResultSet-and-DataTable%29-tf4314874.html#a12306193
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
