Re: java stored procedures fast, but slow when called as SQL function

From: Peter J. Holzer <hjp-usenet_at_hjp.at>
Date: Tue, 15 Apr 2003 18:15:35 +0200
Message-ID: <slrnb9oc17.4cd.hjp-usenet@teal.hjp.at>

On 2003-04-15 07:17, Norman Dunbar <Norman.Dunbar_at_lfs.co.uk> wrote:

>>> UTL_FILE will read and write files as user
>>> oracle, so different database users can access each other's files and

> it

>>> is important to restrict file access to a directory.

>
> Since 9i release 2 this is no longer an issue. Rather than specifying
> UTL_FILE_DIR in the init.ora file, you now create an oracle directory
> which points at a specific folder/directory and give individual users
> read and/or write privs to the oracle directory.

Nice.

> PS. When I was at college, Virtual Machine meant just that - you
> appeared to have the entire resources of the machine to yourself. As far
> as I know, the meaning hasn't changed,

Yup. That meaning of VM is still very much alive. See VMware or IBM hosts.

> it has just been 'leveraged' (aaarrgh !) to mean something totally
> different. A Java VM is just (!) an interpreter while a VM is
> something to do with multi-user systems.

Pretty much the same thing. A physical machine is only an interpreter built in hardware (and with CPUs like the P4 or the Transmeta Crusoe they even include a JITC).

So, with IBM VM or VMware, you create one or more virtual machines (instances of interpreters) which look (mostly) the same as the one they are running on.

With binary emulators like Wabi, StonX, or whatever, you create virtual machines which look like a different physical machine.

And with JVM, the UCSD p-code system, etc. you create virtual machines which were never implemented in hardware (you could, though).

        hp

-- 
   _  | Peter J. Holzer    | Latein ist das humanoide Äquivalent
|_|_) | Sysadmin WSR       | zu Fortran.
| |   | hjp_at_hjp.at         |
__/   | http://www.hjp.at/ |    -- Alexander Bartolich in at.linux

Received on Tue Apr 15 2003 - 11:15:35 CDT