, September 25, 2001 1:43 AM
Subject: Re: [JBoss-dev] EJB/QL - JBoss extentions
My idea is to not use remote objects _at all_ and just have data
copies. There are many situations where entity ejbs are not appropriate,
and a lot of them stem from a need to get a quick copy of a _lot_ of
data. The key
, 2001 1:43 AM
Subject: Re: [JBoss-dev] EJB/QL - JBoss extentions
My idea is to not use remote objects _at all_ and just have data
copies. There are many situations where entity ejbs are not appropriate,
and a lot of them stem from a need to get a quick copy of a _lot_ of
data. The key
implementation of jboss alpha ?
Tbone,
Original Message -
From: Dmitri Colebatch [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, September 25, 2001 11:34 PM
Subject: Re: [JBoss-dev] EJB/QL - JBoss extentions
On Tue, 25 Sep 2001, Philip Van Bogaert wrote:
You are so right,
I think
on 1-09-24 05.36, Dain Sundstrom at [EMAIL PROTECTED] wrote:
Maybe I am stupid, but I have have no idea what this means.
I do not think so ! ... it is me being unclear -perhaps ... -this means, A
pattern is great, and especially so, if there is a good implementation
template I can use, and
Hi,
Yes, I am working on this. Here is the algorithm. The list of PK
values are loaded at first and stored to LRU cache of query results on
server, the id of the list is passed to client. When client requests
some CMP field, the list id and index in the list of the given entity
is passed to
Close, but what if my initial list is 1 million records. That means that
you still have to load and create 1 million pk's. I think you need to
define the query and return the list. When the Collection asks for the
next record or record # 10 then you not only need to load the record but
also
Dave Smith wrote:
Close, but what if my initial list is 1 million records. That means that
you still have to load and create 1 million pk's. I think you need to
define the query and return the list. When the Collection asks for the
next record or record # 10 then you not only need to load
your sentences short and
clear.
Thanks
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Peter
|Fagerlund
|Sent: Monday, September 24, 2001 7:30 AM
|To: [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] EJB/QL - JBoss extentions
|
|
|on 1-09-24 05.36
Keep the result set open, retieve from the set as necessary, probably
using a cursor. That way if someone is doing a search that has 1 million
records and after I display the first 10 and the client chooses the 3rd
one, we have only created 10 objects.
Oleg Nitz wrote:
Dave Smith wrote:
As normal dain converts my ramblings into good ideas .. Comments below ..
I suggest that we add an order element to the query section in
jbosscmp-jdbc.xml file. Something like
query
descriptionFind all orders with the specified status/description
query-method
Dave Smith wrote:
Keep the result set open, retieve from the set as necessary, probably
using a cursor. That way if someone is doing a search that has 1 million
records and after I display the first 10 and the client chooses the 3rd
one, we have only created 10 objects.
No, no, no! We
Oleg Nitz wrote:
Dave Smith wrote:
Keep the result set open, retieve from the set as necessary, probably
using a cursor. That way if someone is doing a search that has 1 million
records and after I display the first 10 and the client chooses the 3rd
one, we have only created 10 objects.
comments below...
4. database functions
If I am doing a query on a datestamp type field but I only
care about
the date part, in postgresql I need to use a postgresql
function that
only returns the date.
Date handling is EJB-QL sucks. Here is how you can do it
myRef.date =
hey list,
I'm not sure where to start with this, as I haven't contributed anything
(yet), but spent last weekend on something that I think is (partially)
relevant here. I wasn't going to post this message until next weekend
when I should have some time to clean some of my work up, but...
If
Ok, so 20 or so e-mails later the summary ..
1) Right now if I want to use order I have to use declared-sql with an
order by clause but dain wants to add an order tag to the xml config file.
2) For dynamic queries I just use declared-sql and do my normal SQL
query. This could also be used if
Dave Smith wrote:
Keep the result set open, retieve from the set as necessary, probably
using a cursor. That way if someone is doing a search that has
1 million
records and after I display the first 10 and the client chooses the 3rd
one, we have only created 10 objects.
No, no, no! We
-Original Message-
From: Ignacio Coloma
To: [EMAIL PROTECTED]
Sent: 9/24/01 3:00 PM
Subject: RE: [JBoss-dev] EJB/QL - JBoss extentions
Dave Smith wrote:
Keep the result set open, retieve from the set as necessary,
probably
using a cursor. That way if someone is doing a search that has
1
See below ..
Ignacio Coloma wrote:
Dave Smith wrote:
Keep the result set open, retieve from the set as necessary, probably
using a cursor. That way if someone is doing a search that has
1 million
records and after I display the first 10 and the client chooses the 3rd
one, we have only
operations).
Where the SessionBean does one request and returns an amouth of objects to
the clients on he's request
Tbone
- Original Message -
From: Dmitri Colebatch [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 24, 2001 5:10 PM
Subject: Re: [JBoss-dev] EJB/QL - JBoss
I always think the best solution is to ask the right question so there are
= 7 pieces of info in the answer;-)
A couple months ago there was an enormous discussion of this in the
firebird development list -- we ended up impelementing limit and skip. The
solution you propose has a problem if
Ooops.
Thanks for enlightening me this time. Will be more careful on the next :)
-Mensaje original-
De: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]En nombre de David
Jencks
Enviado el: lunes, 24 de septiembre de 2001 21:08
Para: [EMAIL PROTECTED]
Asunto: Re: [JBoss-dev] EJB/QL
operations). Where the
SessionBean does one request and returns an amouth of objects to the
clients on he's request
Tbone
- Original Message -
From: Dmitri Colebatch [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 24, 2001 5:10 PM
Subject: Re: [JBoss-dev] EJB/QL
,
otherwise, I will implement them after spec compliance.
See my comments below.
-Original Message-
From: Hunter Hillegas [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 21, 2001 3:11 PM
To: JBoss Dev
Subject: Re: [JBoss-dev] EJB/QL - JBoss extentions
See my comments below
on 1-09-23 21.17, Dain Sundstrom at [EMAIL PROTECTED] wrote:
2. No limit/offset or cursors.
In a word searches. If you are tring to search for
something you display
a list of current values based on a selection criteria. What happens
when the list is 100,000 records. With current DB code
2. No limit/offset or cursors.
In a word searches. If you are tring to search for
something you display
a list of current values based on a selection criteria.
What happens
when the list is 100,000 records. With current DB code you
would declare
a cursor or use offset and limits
on 1-09-23 22.02, Dain Sundstrom at [EMAIL PROTECTED] wrote:
The blueprint
(http://java.sun.com/j2ee/blueprints/design_patterns/page_by_page_iterator/i
ndex.html) applies to client access of the result set. The problem is the
blueprint assumes that then entire result set of the query can
The blueprint
(http://java.sun.com/j2ee/blueprints/design_patterns/page_by_page_iterator/i
ndex.html) applies to client access of the result set. The problem is
the
blueprint assumes that then entire result set of the query can fit into
server memory.
The implementation do not assume
Dave Smith wrote:
3. Dynamic where clause
Prompting the user for a search criteria and returning a result set
based on those criteria. Also would be handy to have cursors/limit.
[snip]
For 1,3,4 I would propose that we add a special jboss function into the
QL, something like
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|Victor Langelo
|Sent: Friday, September 21, 2001 4:35 PM
|To: [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] EJB/QL - JBoss extentions
|
|
|Dave Smith wrote:
|
| 3. Dynamic where clause
| Prompting the user
29 matches
Mail list logo
