Hi there,
I have a large multi module project which is working well.
Now i'm trying to enhance this with a things which is in relationship
with the database...
Ok i decided to take a look at the sql-maven-plugin to execute some SQL
statements before an integration test is run (simply delete t
You are missing a space in your sql query after the *.
-ketil
On Thu, Apr 23, 2009 at 10:47 AM, Karl Heinz Marbaise wrote:
> Hi there,
>
> I have a large multi module project which is working well.
> Now i'm trying to enhance this with a things which is in relationship with
> the database...
>
>
And table is a reserved word in sql, so you should insert your real
table name there.
-ketil
On Thu, Apr 23, 2009 at 10:47 AM, Karl Heinz Marbaise wrote:
> Hi there,
>
> I have a large multi module project which is working well.
> Now i'm trying to enhance this with a things which is in relation
Hi,
You are missing a space in your sql query after the *.
I changed it..."SELECT * FROM table", but the reaction was the same and
i excepted nothing else, cause the syntax does not require a space...
On the other hand the problem seemed to more located into the area of
the lifecycle cause th
Hi,
And table is a reserved word in sql, so you should insert your real
table name there.
Yes of course i know...in the real example here i have a real table
name, but i don't want to write real names in the post into the mailing
list...
Kind regards
Karl Heinz Marbaise
-ketil
On Thu, Apr 2
Well, the exception raised is caused by an SQLException, and it seems
to say that you have an illegal argument in your query if my german is
not all wrong.
Caused by: java.sql.SQLException: Ungłltige Argumente in Aufruf
-ketil
On Thu, Apr 23, 2009 at 11:08 AM, Karl Heinz Marbaise wrote:
> Hi,
>
Hi,
Well, the exception raised is caused by an SQLException, and it seems
to say that you have an illegal argument in your query if my german is
not all wrong.
Caused by: java.sql.SQLException: Ungłltige Argumente in Aufruf
Correct...(Your knowledge of german is not wrong ;-))...
But now i si
Hi there,
after a longer break i found the issue based on the suggestions of You...
${database.username}
it simply has to be changed into ${database.user} so it was simply not
using the correct propertyfor the username...
I was a little bit confused based on the stack trace...;-(
Ma
