Are you sure you want?
- Thread starter mbo
- Start date
There is no preference for this, so you can only avoid it by specifying a where clause. A dummy where clause (where 1=1) would of course be more work than acknowledging the confirmation.
------------------
Marco Kalter
Allround Automations
------------------
Marco Kalter
Allround Automations
Hi Mark,
AAAAAARRRRRGGGHHHH!
Thanks for your quick answer.
This kind of "improvement" is an actual regression of PlSql Dev.
I have to work fast and don't need any initiative of my tool (and PlSql Dev is a very good tool).
Please consider that PlSql is used by professionals who know what they do (and can use rollback is they need it). Don't modify you wonderfull product in that stupid direction (or make it customisable).
Can we hope a modification of that faulty behaviour in future version?
best regards,
Mbo
AAAAAARRRRRGGGHHHH!
Thanks for your quick answer.
This kind of "improvement" is an actual regression of PlSql Dev.
I have to work fast and don't need any initiative of my tool (and PlSql Dev is a very good tool).
Please consider that PlSql is used by professionals who know what they do (and can use rollback is they need it). Don't modify you wonderfull product in that stupid direction (or make it customisable).
Can we hope a modification of that faulty behaviour in future version?
best regards,
Mbo
It's a matter of opinion if you think this is "faulty behaviour". We added this because people lost data and asked for this safety net.
We have changed this slightly for our soon to be released version 5.1.3 where you will only get this warning once for the duration of a PL/SQL Developer "session" (not a database session). If you press the OK button once, PL/SQL Developer assumes that subsequent deletes and updates without a where clause are also OK.
------------------
Marco Kalter
Allround Automations
We have changed this slightly for our soon to be released version 5.1.3 where you will only get this warning once for the duration of a PL/SQL Developer "session" (not a database session). If you press the OK button once, PL/SQL Developer assumes that subsequent deletes and updates without a where clause are also OK.
------------------
Marco Kalter
Allround Automations
Thanks for this information marco,
I will download 5.1.3 version as soon as possible.
Please make this behaviour customisable. This way you won't impose "people" opinion to everybody any more.
Once again data safety can be ensured by database itself with backups, rollbacks, and with Oracle 9i you can get back datas even after delete+commit.
At this point it's nearly philosophy but "safety" net imposed to everybody because of "people" can quicly lead to hell on hearth.
Keep PlSql dev efficient it's my favorite tool.
Best regards,
Marc.ResponsiveOfMyActs
I will download 5.1.3 version as soon as possible.
Please make this behaviour customisable. This way you won't impose "people" opinion to everybody any more.
Once again data safety can be ensured by database itself with backups, rollbacks, and with Oracle 9i you can get back datas even after delete+commit.
At this point it's nearly philosophy but "safety" net imposed to everybody because of "people" can quicly lead to hell on hearth.
Keep PlSql dev efficient it's my favorite tool.
Best regards,
Marc.ResponsiveOfMyActs
