BTW, most DB's varchars I've used crack whenever I want to store more than
8k... And sometimes even less
> -----Original Message-----
> From: KirkYarina [mailto:[EMAIL PROTECTED]]
> Sent: Viernes, 02 de Febrero de 2001 13:54
> To: [EMAIL PROTECTED]
> Subject: Re: bean design problem for one to many relationship
>
>
> Could you expand upon this a bit. How would you recommend
> handling a field
> that's potentially larger than available memory, such as an
> image or very
> large text file?
>
> Kirk Yarina
>
> At 03:38 PM 2/1/01 -0800, you wrote:
> > > From: A mailing list for Enterprise JavaBeans development
> >
> > > You mention that "There is some limitation using BLOB on some
> > > application servers (such as
> > > with WLS)" I am using WLS. Would you please say a little
> bit more what
> > > the limitation is? or
> > > recommend me some references to me about this?
> >
> >It is usually not recommended to store Java BLOB's for
> several reaons:
> >
> >- poor performances (serialization is expensive)
> >- versioning issues
> >- no queries possible
> >- and others...
> >
> >The time you will spend making your object a "real" Entity
> bean will be
> >more than
> >paid off by the functionalities and performances that both
> the container
> >and the
> >database will bring you.
> >
> >Even more so if you're using an EJB 2.0 container.
> >
> >--
> >Cedric
>
> ==============================================================
> =============
> To unsubscribe, send email to [EMAIL PROTECTED] and
> include in the body
> of the message "signoff EJB-INTEREST". For general help,
> send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
