I'm quoting this message from Bryan, that replyed in another thread due to
post pending in this thread. I preferred to answer here for the context of
the argument.
(this is the link of the other thread:
Can anyone explain what this means? It occurs when I issue what should
be a straightforward insert:
INSERT INTO resource_usage (resid,xmlid,xmltable)
(SELECT resid,?,? FROM resource_usage WHERE xmlid=? AND xmltable=?)
The select returns 64 results, but the ibsert fails.
Interesting, Pablo! Thanks, I'll give a test drive!
Dag
John English j...@brighton.ac.uk writes:
Can anyone explain what this means? It occurs when I issue what should
be a straightforward insert:
INSERT INTO resource_usage (resid,xmlid,xmltable)
(SELECT resid,?,? FROM resource_usage WHERE xmlid=? AND xmltable=?)
I think we had a similar
On 12/07/2010 12:15 PM, John English wrote:
Can anyone explain what this means? It occurs when I issue what should
be a straightforward insert:
INSERT INTO resource_usage (resid,xmlid,xmltable)
(SELECT resid,?,? FROM resource_usage WHERE xmlid=? AND xmltable=?)
The select returns 64 results,
My app is made of a login-server connected with embeddeddriver to the derby,
and another server that needs to connect too to the database.
You can use what is called the Embedded Server, where one program directly
accesses the database using the embedded driver, while that same program
also
