Triggers and bits

[LuckyJim1001]

Hi all,

Apologies for a complete noob post in advance.

I am working my way through learning PL/SQL and i am using a test database at work to this end. So far I have done a few Inserts, Updates and the odd delete.

Now the database I have been working on has, according to the software duppliers, 'become corrupt' and they need to 'recompile the source code'

So have I done something to break the DB ?

With regards to Triggers and indexes, which apparently because I did not use thier front end, got 'screwed up' I though that Triggers fired no matter what.

That is if I use SQL*Plus or thier front end the Triggers still fired.

Am I getting this wrong, and I do apologise again fro such a noob question

many thanks.

[davey23uk]

depends what is in the trigger - and what their definiton of corrupt is

[LKBrwn_DBA]

Hi all,

Apologies for a complete noob post in advance.

I am working my way through learning PL/SQL and i am using a test database at work to this end. So far I have done a few Inserts, Updates and the odd delete.

Now the database I have been working on has, according to the software duppliers, 'become corrupt' and they need to 'recompile the source code'

So have I done something to break the DB ?

With regards to Triggers and indexes, which apparently because I did not use thier front end, got 'screwed up' I though that Triggers fired no matter what.

That is if I use SQL*Plus or thier front end the Triggers still fired.

Am I getting this wrong, and I do apologise again fro such a noob question

many thanks.

Seems to me they are feeding you some BS. No amount of Inserts, Updates and the odd delete will make the programs/procedures 'become corrupt' and in need to 'recompile the source code'.

Now, if you did some changes to the schema (tables/views structure) like adding/removing columns then maybe the stored procedures or other programs would need to be re-compiled.

Inserts, Updates and the odd delete could corrupt the data, but NOT the programs.