Message-
> From: [EMAIL PROTECTED]
[mailto:hibernate-devel-
> [EMAIL PROTECTED] On Behalf Of Brad Clow
> Sent: Monday, December 23, 2002 7:49 AM
> To: Mark Woon
> Cc: [EMAIL PROTECTED]
> Subject: RE: [Hibernate] Road Map
>
> use proxies if u want to lazy load objects.
>
use proxies if u want to lazy load objects.
brad
>
> I'd also love to see the ability to lazy-load objects instead of just
> collections...
>
> -Mark
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.c
unday, December 22, 2002 7:29 PM
Subject: RE: [Hibernate] Road Map
> Btw while we're talking about eager loading or lazy loading things...
> how do you find the idea of providing a dynamic mechanism to specify at
> runtime for each scenario which parts should be loaded eagerly
whoops - forgot to correct the reply address so here it goes again :)
- Original Message -
From: "Max Rydahl Andersen" <[EMAIL PROTECTED]>
To: "Gavin King" <[EMAIL PROTECTED]>
Sent: Sunday, December 22, 2002 6:24 PM
Subject: Re: [Hibernate] Road Map
>This one is going to be fuun :) (You didn't follow up on the discussion
> on identity for these "value beans" - was it just to insane or ? :)
I think we need to maintain a strict distinction between "value types"
and "entity types". These value beans shouldn't have any notion of
identity because
Gavin King wrote:
The only caveat is that I implemented the writes
such that it
truncates the stream since that's the behavior I wanted.
Would you enlarge on this please? I'm not quite sure what
you're getting at
Say you have a Clob of length 10. If you're at position 4, and you
Gavin King wrote:
P.S. I've never figured out IIRC.
If I Remember Correctly.
-Mark
---
This SF.NET email is sponsored by: Order your Holiday Geek Presents Now!
Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap,
MP
On 22 Dec (10:44), Gavin King wrote:
> I agree with this. It is the resposibility of the middle tier
> to fetch data. If it did not fulfil its part of the contract,
> we can't just have the web tier suddenly open connections to
> the database. That has all *kinds* of security implications.
>
> >
I agree with this. It is the resposibility of the middle tier
to fetch data. If it did not fulfil its part of the contract,
we can't just have the web tier suddenly open connections to
the database. That has all *kinds* of security implications.
> I can't see any other decent way - the View laye
> Some people mentioned that they implemented applications with Hibernate
> and put them in production. I've achieved that too, but only the
> classic JSP/Servlet/DataAccess Webapp. Has anyone implemented a
> three-tier system with Hibernate and lazy collections yet?
Depends on what you mean by t
>Hibernate 2.0 beta
>==
>* create a new module in CVS with improved directory
> structure
Yes! :)
> * rename packages to net.sf.hibernate
Yes! :)
>* replace existing configuration mechanisms
> with an interface that unifies the functionality
> of HibernateService, (the misna
> Attached.
Looks to be exactly what we need.
> The only caveat is that I implemented the writes
> such that it
> truncates the stream since that's the behavior I wanted.
Would you enlarge on this please? I'm not quite sure what
you're getting at
** CAUTION - Disclaimer
>
> Hmm... I'm not sure I understand. Won't calling setString() negate
> some the memory benefits of using a Clob (ie. not everything
> needs to be
> in memory)? I guess I'll wait and look at the code.
Only when first *creating* a Clob. When, presumably, you have the whole
thing in memory
> I'm pretty
> sure this won't work for some db's. I know it won't work in
> Oracle due
> to their JDBC drivers. Here's a summary of my discoveries:
>
> 1) I was under the impression that I could just use my own Clob
> implementation and call PreparedStatement.setClob.
> Unfortunately, t
On 20 Dec (17:58), Mark Woon wrote:
> >Yes, but closing/disconnecting the Session is _not_ the real problem.
> >The problem is: How and where does the Filter/Observer get and store the
> >Session to do its work?
> >
> >
>
> Ah. I'm storing it in the request attributes. If a page needs a
> Ses
Christian Bauer wrote:
On 20 Dec (17:37), Mark Woon wrote:
Have you considered using a filter to close the Session after everything
is rendered?
Yes, but closing/disconnecting the Session is _not_ the real problem.
The problem is: How and where does the Filter/Observer get and store the
On 20 Dec (17:37), Mark Woon wrote:
> Have you considered using a filter to close the Session after everything
> is rendered?
Yes, but closing/disconnecting the Session is _not_ the real problem.
The problem is: How and where does the Filter/Observer get and store the
Session to do its work?
--
Christian Bauer wrote:
While I'm at it: Another rework, or at least a discussion about it, for
2.0 would be the automatic reconnect of Sessions. You once mentioned
that in a forum post, but didn't like it.
My two cents:
If you've learned the basic concepts of O/R mapping, it's easy to produce
Gavin King wrote:
How are you planning on supporting this? Is there going to be some
internal changes in Hibernate to support them, or are you
just going to
add new Blob and Clob types?
There are two parts to this new functionality. Firstly, there is the
existing (in CVS) BlobType and C
On 21 Dec (11:48), Gavin King wrote:
> I'm not actually sure that there are any commonly accepted
> names for this pattern. The Hibernate Session is *almost*
> similar to UnitOfWork except for the fact that it is _not_,
> actually, an atomic unit of work. Neither is it quite like
> the ODMG Datab
> When I had a first look at the JDO API, I really liked
>
> PersistenceManagerFactory
> PersistenceManager
Hmmm I find "Manager" even more banal (and overloaded)
than "Session". Anyway the Hibernate Session doesn't
seem to me to fit the description of "Manager" (which
carries connotations of si
>
> >Future plans:
> >
> >Next release: 1.2.1
> >===
> >* various bugfixes
> >* full support for Clob and Blob
> >
>
> How are you planning on supporting this? Is there going to be some
> internal changes in Hibernate to support them, or are you
> just going to
> add new Blob
On 21 Dec (11:48), Gavin King wrote:
> LOL :))
>
> I'm not actually sure that there are any commonly accepted
> names for this pattern. The Hibernate Session is *almost*
> similar to UnitOfWork except for the fact that it is _not_,
> actually, an atomic unit of work. Neither is it quite like
> t
Gavin King wrote:
Future plans:
Next release: 1.2.1
===
* various bugfixes
* full support for Clob and Blob
How are you planning on supporting this? Is there going to be some
internal changes in Hibernate to support them, or are you just going to
add new Blob and Clob types?
which, by their
names, imply a long-lived, singleton-style object.
> -Original Message-
> From: Christian Bauer [mailto:[EMAIL PROTECTED]
> Sent: Saturday, 21 December 2002 11:33 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Hibernate] Road Map
>
>
> On 21 Dec (11:15
On 21 Dec (11:15), Gavin King wrote:
> I suspect that many people would be tempted to vote for (2).
> But is there really *that* much value in that for the users?
> The interfaces themselves arent changing, so its a simple
> search/replace followed be recompile.
Maybe this recommendation is a bit
Future plans:
Next release: 1.2.1
===
* various bugfixes
* full support for Clob and Blob
* FlushMode API + deprecation of suspend/resumeFlushes
* Improved logging of bind variables, etc.
1.2.1 is almost ready to go. Should be released in one
to two weeks. This will be a very st
27 matches
Mail list logo
