Hello,
just wanted to check if this behavior is on purpose.
For select Statements I use the following construct in my DAO.
public List selectJobs() {
List resultList = null;
SqlSession session = getSqlSessionFactory().openSession();
try {
JobMapper mapper
I'm evaluating the technology and have a "tricky" startup problem I'm not
able to "see" the solution for.
I get the:
Exception in thread "main" org.apache.ibatis.exceptions.IbatisException:
### Error building SqlSession.
### The error may exist in test/ibatis/Account.xml
### Cause: org.apache.ibat
Jon,
Verify if Account.xml is in correct format. It should contain
http://ibatis.apache.org/dtd/ibatis-3-mapper.dtd";>
instead of
http://ibatis.apache.org/dtd/sql-map-2.dtd";>
to begin with.
Regards.
On 17/03/2010 10:39, Jon Finanger wrote:
I'm evaluating the technology and have a "tricky"
Hi!
I have default configuration "time_zone=GMT+0:00"
and I'm now in the EET time zone (GMT+2:00)
I executed "migrate new blah"
and got a script called "20100317163912_blah.sql"
and my clock shows "2010-03-17 16:39"
I expected to got script called "20100317143912_blah.sql"
Could you please help
Thanks,
Hmm...missing some letters there I see...
Got a step furtherthe 3 version differs a bit from the 2 version I
realize. Since the version 3 lacks some documentation i learn quite a bit
from the error messages :-)
-Jon
-Original Message-
From: Eduardo M. Cavalcanti [mailto:ecav
Looks good.
Thanks
orb
Fra: Clinton Begin [[email protected]]
Sendt: 17. mars 2010 05:28
Til: [email protected]
Emne: Re: setNull and default jdbcType
Fixed. Give it a try.
Clinton
On Tue, Mar 16, 2010 at 12:28 PM, Bekkum Odd-Rune
mailto:odd-ru
If there's documentation lacking, please contribute it as per the note
within the first couple of pages of the user guide.
On 2010-03-17, Jon Finanger wrote:
> Thanks,
> Hmm...missing some letters there I see...
> Got a step furtherthe 3 version differs a bit from the 2 version I
> realize.
Actually, I just checked, the XML Headers appear on pages 5 and 7 of the
user guide, for the config and mapper DTDs respectively.
If you have a recommendation to make it clearer, add it to the documentation
contribution site.
http://opensource.atlassian.com/confluence/oss/display/IBATIS/Contribut
Hi
I have not heard back from anyone on this issue (which I am running into), is
it a bug or a non-issue?
I went back and retested it and I get the "CommunicationsException" with the
POOLED data source as well (so my original testing was not up to par).
For me this will require some amount of
Andrius
Like Simo I like option 1, it is probably the simplest option. 3 could really
ugly and pushes functionality down into the RBDMS which is not great for
scaling, also adds overhead to any insert/update/delete operations.
One think you might consider (which I do for a project I am working
I think I just ran into a small issue. I have the follow in my mapper
interface. The second method has the sql defined in a XML file.
@Select("select Clients.* from Clients, Accounts where Accounts.id =
Clients.accountId and Accounts.id = #{accountId} order by name")
public List listForAccount
Hi,
If I end up using iBaits i'll definitely try to contribute.
I like the concept
-Jon
Actually, I just checked, the XML Headers appear on pages 5 and 7 of
the user guide, for the config and mapper DTDs respectively.
If you have a recommendation to make it clearer, add it to the
documentat
Hi all,
I am trying to accomplish an obscure use-case. I am trying to
implement the generation of a Postgres function (aka stored procedure)
via iBatis. I am using an tag and simply have the standard
PostgreSQL syntax for creating the funciton within it. I created all
this functionality throug
Oh - I forgot to mention a few other details.
* I am using the iBatis spring integration (ibatis-sqlmap-2.3.0.jar,
spring-ibatis-2.0.8.jar)
* The weirdest part here is that the code fully works when I run it
through a unit test, but when I run it as a deployed webapp, it fails.
On Wed, Mar 17,
I'm not following your situation. You say it works fine through a unit
test but fails in Tomcat. By fine, do you mean that you can create your
stored proc via iBATIS in your unit test? If so and it fails on your
webapp, then I'm guessing your webapp is using $ signs for other
purposes. You
I'm not sure what to say... this is not really an iBATIS issue.
* First, you're purposefully going directly against a key part of the
SqlSession contract. There's an entire section in the user guide about
SqlSession lifecycle (Page 9) and you're completely ignoring it. This makes
it very diffi
16 matches
Mail list logo