The tables are being used for dynamic update and count of notification whenever a pre-defined change is made in any of the columns. Also, I had posted the trigger statement in a simplified form omitting data from it for which I knew I could work on myself.
Hope that answers your query.
Can you help me with one more transformation??
select * TABLEA where uid in (101,102,103) order by creation_time limit 5"
The problem here is with the 'limit 5' part of the query
Also, can you let me know of any online tutorial help available for learning Derby Query basics ??
"Bernt M. Johnsen" <Bernt.Johnsen@Sun.COM> wrote:
>>>>>>>>>>>> Aneez Backer wrote (2007-11-21 20:05:01):
> Thanks Bernt.
> That helped
Just a small question: Is there some special (e.g. performance)
requirements that force you to maintain the data in TABLEB? Since
SELECT TAGCOUNT FROM TABLEB WHERE ID=xxx;
should give the same result as
SELECT COUNT(TAG_ID) FROM TABLEA WHERE TAG_ID=xxx;
you could perhaps do without the triggers and TABLEB?
Bernt Marius Johnsen, Database Technology Group,
Staff Engineer, Derby/Java DB
Sun Microsystems, Trondheim, Norway