On 15/11/06, Keith Irwin <[EMAIL PROTECTED]> wrote:
Folks---
I want to run something similar in a single transaction (just a loop
that runs each query one after another then commits):
Assuming table (shorthand):
order (order_id autoincrement, name)
items (item_id autoincrement, order_id,
Folks---
I want to run something similar in a single transaction (just a loop
that runs each query one after another then commits):
Assuming table (shorthand):
order (order_id autoincrement, name)
items (item_id autoincrement, order_id, name)
And queries:
insert into orders (name) valu
On 15/11/06, Stanley Bradbury <[EMAIL PROTECTED]> wrote:
Duncan Groenewald wrote:
> Does derby support transaction logging ? and if so how to dump/access
> them ? If not any plan to do so ??
>
I don't understand what you are asking about but can tell you that Derby
maintains a transaction log fo
I'm the lead developer of the Mondrian ROLAP server, and I confess that
Mondrian generates SQL just like this too. The SQL is unpleasant, but when
you want to 'join' a large array of values in memory to a database table,
the SQL language doesn't present any better alternatives. Writing the values
t
Duncan Groenewald wrote:
Does derby support transaction logging ? and if so how to dump/access
them ? If not any plan to do so ??
I don't understand what you are asking about but can tell you that Derby
maintains a transaction log for rollback and recovery purposes. It is
not intended to be
If rewriting the query is not an option, what alternatives are there to
overcome this limitation?
What version of Derby are you using? (Apologies if you already said that
and I missed it). If you are using a version prior to 10.2, you should
definitely try 10.2, as there was a *lot* of work in t
I'm sorry to tell you, but what a database is supposed to do is to
return data based on syntactically and semantically valid queries. This
means that even if you have an extremely stupid but valid query, it
should execute. One thing to do is to impose some well defined server
limitations, which
Ok.
Sigh.
It's early in the morning and I haven't had my first cup of coffee.
If we were in the same office, I'd roll up the C section of the WSJ and
politely bop you on the head saying "Bad boy! Bad boy! Did you do this?"
This is yet another example of a maxim :
"Just because you can
The query from the attached log file is:
UPDATE task_config_permission SET default_value=NULL
WHERE task_type_id IN (SELECT id FROM task_type WHERE proj_id=?)
AND CAST(default_value AS INTEGER) NOT
IN(0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,
