The disconnect doesn't really disconnect, it just places the
connection back into the appserver's jdbc pool. I still think
you're on to something, since the next time you might get a
different connection. I don't know if the DB maintains the
statements across connections. Some might... Good question.
Frank
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jerry King
> Sent: Monday, September 18, 2000 5:50 PM
> To: [EMAIL PROTECTED]
> Subject: Entity Beans and Prepared Statements
>
>
> Does it ever make sense to use prepared statements with
> Entity Beans? Since
> prepared statements are associated with a single db
> connection, you would be
> bypassing the db connection pooling of the application
> server. From most
> examples I have seen, the entity bean calls (ejbCreate,
> ejbRemove, ejbLoad,
> ejbStore) establish a connection to the database, perform an
> action, and
> disconnect from the database. By disconnecting from the database, the
> prepared statement will be invalid. Has anyone found a way
> to prepared
> statements in conjunction with Entity Beans?
>
> Thanks,
> Jerry King
>
> ==============================================================
> =============
> 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".
