I could use this
feature, too. However, not *every* column is like this in our
case.
Our convention is
tables have 4-letter abbreviations and are prefixed with a "T". For instances,
our customer table is named TCUST_CUSTOMER. The fields within it are prefixed
with CUST, so the name is
This should be in
the docs. I wasn't sure if it was supported, so I tried it and it worked.
Because it's not obvious that multiple groupBy attributes will work, it should
be documented.
-Original Message-From: Jeff Butler
[mailto:[EMAIL PROTECTED]Sent: Friday, October 20, 2006
You're only going to want to create temporary tables when the connection is
created, not at the beginning of every transaction.
Depending on what kind of connection pool you're using, you may be able to use
their connection lifecycle event handler to do this rather than rely on iBATIS
to
This sounds like it could be solved by a connection lifecycle event handler
that Clinton mentioned on Sept. 16th:
http://www.mail-archive.com/user-java@ibatis.apache.org/msg06174.html
Strangely, I've actually needed this functionality before. I created a bunch of
temporary tables with Postgres
I finally found the
docs. They're at http://beehive.apache.org/docs/1.0.1/system-controls/jdbc/guide.html
I'll keep looking at
them, but it would be helpful if someone really knowledgeable in iBATIS could
tell if any important features are missing from BeeHive, or if it has anything
