Help with TOAD

#11

On 16 Feb 2004 22:30:13 +0100, "Peter" <peter@ciber> wrote:

Quote:

What do you guys mean by "dangerous". Do you mean for example that you can
directly meddle with the data and maybe destroy its integrity?

Surely you can bypass the application with Toad, as you can with
sql*plus. This can be dangerous, because you can do *anything*.
However:

You can only destroy it's integrity when there is no integrity in the
database (by means of primary and foreign key constraints) in the
first place.
Which is the default for almost all commercially developed sw
packages, and which is also the default for applications developed by
middle-tier believers.

--
Sybrand Bakker, Senior Oracle DBA

#12

On Mon, 16 Feb 2004 16:48:28 -0500, "Bib Endum"
<gd-newsgroups (AT) spamex (DOT) com> wrote:

Quote:

We're in 2004 and they don't even have command line history in sql*plus for
windows for god's sake.

and who needs it anyway? You can save your command to a file.
Also, i*sqlplus in 9i comes with command line history, AFAIK.
Probably you are referring to a paleolithic version.

--
Sybrand Bakker, Senior Oracle DBA

#13

Bib Endum wrote:

Quote:

"Jeff Smith" <jsmit234 at ford dot com> a écrit dans le message de
news:c0qkae$pg25 (AT) eccws12 (DOT) dearborn.ford.com...
You better be darn careful if *you* are going mess around in your database
with something like Toad.

Always depends on who is behind the wheel.

Very true. Always dangerous having Turkeys drive Toads.

Quote:

Yes it's easy to mess around with TOAD, but a lot more efficient to work
with than using sql*plus or OEM with the DBA module. Have you ever worked
with Oracle procedure editor ? That's total bullshit compared to any decent
and modern PL/SQL editor.

So use the PL/SQL editor/debugger that's included in JDeveloper. Much
better, and - if you use the downloaded one - free.

Quote:

We're in 2004 and they don't even have command line history in sql*plus for
windows for god's sake.

If you use this in Windows, use the DOS version and enable the DOS
command line history. Same thing as the PlusW, just not as colourful.

Quote:

Also, there is a way to make TOAD less dangerous by removing buttons and
menu item for oneself or for others.

<observation>
However, my experience is that people who are comfortable with SQL*Plus
tend to be slightly more cautious. The majority of those I know who use
TOAD tend to want be 'first to the finish lie' rather than 'safely to
finish line'. Does not imply that Toad is bad - quite the opposite,
it's a good tool. Just means I've noticed that people with a certain
attitude toward development tend to use some kinds of tools as props.
<\observation>

/Hans

#14

Single click in TOAD can cause unwanted action on database

In sqlplus is takes a typed command.

"Sybrand Bakker" <gooiditweg (AT) nospam (DOT) demon.nl> wrote

Quote:

On Mon, 16 Feb 2004 09:42:21 -0800, "Ron" <support (AT) dbainfopower (DOT) com
wrote:

Good for developer - IMHO - never to be used in production!

Nonsense. Sql*plus is just as dangerous in production as Toad,
especially if there is not RI in the database (which is the default
with US software)

--
Sybrand Bakker, Senior Oracle DBA

#15

"Hans Forbrich" <hforbric (AT) yahoo (DOT) net> a écrit dans le message de
news:40315A7C.66B02DD4 (AT) yahoo (DOT) net...

Quote:

So use the PL/SQL editor/debugger that's included in JDeveloper. Much
better, and - if you use the downloaded one - free.

Didn't know about this one. We are not really into the Java bandwagon here,
and last time I checked Jdev, when I started it on my workstation, the
lights dimmed in the office.

Quote:

If you use this in Windows, use the DOS version and enable the DOS
command line history. Same thing as the PlusW, just not as colourful.

Good. I knew you could do that under UNIX, but for some reason it never
worked well for me, so I stopped bothering about that under UNIX, might
depend on the shell you use. You might have to use a shell with command line
history (Like tcsh, bash) for this to work. I checked on Windows 2000 and it
works great. All I miss is the scrollbars... but I can live with it.

#16

Bib Endum wrote:

Quote:

"Hans Forbrich" <hforbric (AT) yahoo (DOT) net> a écrit dans le message de
news:40315A7C.66B02DD4 (AT) yahoo (DOT) net...

So use the PL/SQL editor/debugger that's included in JDeveloper. Much
better, and - if you use the downloaded one - free.

Didn't know about this one. We are not really into the Java bandwagon here,
and last time I checked Jdev, when I started it on my workstation, the
lights dimmed in the office.

If you use this in Windows, use the DOS version and enable the DOS
command line history. Same thing as the PlusW, just not as colourful.

Good. I knew you could do that under UNIX, but for some reason it never
worked well for me, so I stopped bothering about that under UNIX, might
depend on the shell you use. You might have to use a shell with command line
history (Like tcsh, bash) for this to work. I checked on Windows 2000 and it
works great. All I miss is the scrollbars... but I can live with it.

there is a freeware prog called "gqlplus" for 'nix'es that makes it act

like sql*plus in a dos window, you can scroll thru your commands with
the up & down arrows. I tried it but in my experience its buffer filled
up & was unuseable, e-mailed the developer and he was having a look at
it, havent heard from him since....

#17

Hans Forbrich wrote:

Quote:

Bib Endum wrote:

"Jeff Smith" <jsmit234 at ford dot com> a écrit dans le message de
news:c0qkae$pg25 (AT) eccws12 (DOT) dearborn.ford.com...

You better be darn careful if *you* are going mess around in your database
with something like Toad.

Always depends on who is behind the wheel.

Very true. Always dangerous having Turkeys drive Toads.

g

Seriously: one can limit TOAD to a read-only tool, by
modifying the licence file. There are several .lic files
in the directory, one is readonly.lic.

--

Regards,
Frank van Bortel