Re: Re: [Hsqldb-user] Triggers and Memory

[fredt <fr...@us...>]

The database engine instantiates one trigger instance per CREATE TRIGGER =
command. There is nothing one can do to avoid this.

Fred
  ----- Original Message -----=20
  From: arm...@fr...=20
  To: hsq...@li...=20
  Sent: 30 March 2004 15:25
  Subject: Re: Re: [Hsqldb-user] Triggers and Memory


  Well, actually my Trigger does nothing. I just initialize it. There is =
absolutely no code in it. But I do it for more than 500 tables, so I get =
over 3000 instances of Triggers (insert, delete, update <-> before, =
after).
  I guess thats the problem.
  It would be sufficient for me to initialize only one Trigger for all =
tables. How can this be done?

  Greetings,
  Armin.



  I suppose it depends on what your triggers do. There is no=20
  indication that a trivial trigger class would increase the ram usage =
by=20
  much.

  Fred

  ----- Original Message -----=20
  From:=20
  Armin=20
  Weiser=20
  To: hsq...@li...=20

  Sent: 29 March 2004 22:25
  Subject: [Hsqldb-user] Triggers and=20
  Memory



  I'm using 1.7.2_RC4 and a=20
  database with CACHED TABLES.
  My application needs about=20
  20 MB of RAM normally.
  When I use triggers for the=20
  tables:

  public class MyTriggers=20
  implements org.hsqldb.Trigger {...

  the used RAM increases to=20
  about 120 MB.
  Do you have any idea how to=20
  decrease the RAM again?

  Many=20
  greetings,
  Armin.

  --
   ------------------------------------------------------- This SF.Net =
email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented =
by Daniel Robbins, President and CEO of GenToo technologies. Learn =
everything from fundamentals to system =
administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dick =
_______________________________________________ Hsqldb-user mailing list =
Hsq...@li... =
https://lists.sourceforge.net/lists/listinfo/hsqldb-user