in reply to Re^2: System Function...script does not move until process ends.
in thread System Function...script does not move until process ends.

I see, but then I don't get it why the use of system seems such a problem.
  1. You initiate a new database,
  2. you stop the old one and unload its data,
  3. you reload the data into the new database.
Seems pretty sequential to me and no need to go into running forks and such.

Or am I missing a fine point here?

CountZero

"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law

Replies are listed 'Best First'.
Re^4: System Function...script does not move until process ends.
by shuchit (Novice) on Apr 07, 2005 at 06:37 UTC

    Or am I missing a fine point here?

    According to what OP is trying to do and what mobigeek posted, to unload data from the old database you need to start the database again. The database (ie. dbeng9) and sql tool (ie. dbisql) are separate processes that have to run at the same time, hence it is not sequential.

    This being said, it is also possible to tell dbisql to automatically start the database itself. So while connecting to the database, dbisql will figure out that the database isn't actually running so it will launch it using the information you provide and then connect to it. See the "start" connection parameter in the online documentation.

[reply]
      Thank you for the very clear explanation. It looks to me that Perl is a bit over-kill here and that a simple shell-script could do the job much easier.

      CountZero

      "If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law

[reply]

In Section Seekers of Perl Wisdom