You can find the full source code for this website in the Seam package in the directory /examples/wiki. It is licensed under the LGPL.
| Online: | 9 Members of 4089 |
| Forum: Seam Users |
23. Jul 2008, 21:50 CET | Link |
Can someone tell me of any problems if I were to use the EntityQuery as a base for querying large number of records in batches?
I think it depends on what do you plan to do with the records.
I believe that imagination is stronger than knowledge -- myth is more potent than history -- dreams are more powerful than facts -- hope always triumphs over experience -- laughter is the cure for grief -- love is stronger than death.
What I am wanting to do is to use the data pagination as a batch fetch. Also, I am wanting to update a field within each record once processed. This would keep me from reinventing the wheel.
One thing that would be nice is to have the
in Seam to be public rather than protected, where it would return the full query string. Useful when instantiating new on EntityQuery and wanting to view the query string or processing transactions using hibernate or some other way.
File a feature request in JIRA
Read about how to report a bug.