Latha, My concept of a "well organized table" includes the idea that all columns have a specific usage. So, if there is some application or audit requirement which calls for a timestamp and 'user' column then, of course, the columns should be created. However, if there are columns which have no use, then I would say that the table is "not well organized".
Just my opinion. :-) Regards, Mike On Thu, Sep 25, 2008 at 1:36 PM, Latha <[EMAIL PROTECTED]> wrote: > I meant "A standard database table" as a "well organized table". > I havent worked into ERP and doesnt have idea about standard tables > available there. > > > On Thu, Sep 25, 2008 at 4:27 PM, rob wolfe <[EMAIL PROTECTED]>wrote: > >> >> I have to pipe in here because there is no such thing as a standard >> database table. There are standard tables for Oracle E-Business suite >> .. but that is not at all the same thing. >> We have to remember on here that while many folks are in an Oracle >> E-Business environment there are just as many, or perhaps more, that are >> not running in that environment. Calling something a "standard database >> table" is a very bad habit to get into especially if you ever take a >> position outside the Oracle E-Business environment because you will be >> in for a rude shock if you expect such niceties as created by, creation >> date, last updated and last updated by to magically exist in tables >> outside that environment. >> >> Sorry if I sound harsh on that but one of my pet peeves is folks that >> are used to working in Oracle Financials (for instance) and think that >> it is the only way to design a database. Not every environment needs the >> amount of , for lack of a better term, extra stuff (like time stamps, >> user stamps .. etc) that an enterprise level ERP system needs and thus a >> lot of them wont have them so don't get used to having them available. >> >> </rant> >> >> Latha wrote: >> > There are several ways. few of them are >> > >> > 1. Capturing the database updates thru log file/table and acquiring >> > the same whenever required. >> > >> > 2. writing a trigger after update >> > >> > 3. A standard database table will always contain the last updated >> > timestamp and last updated user name. it is used to get the recent >> > modified time >> > >> > >> > Regards, >> > Latha >> > >> > On Thu, Sep 25, 2008 at 9:51 AM, dhivya <[EMAIL PROTECTED] >> > <mailto:[EMAIL PROTECTED]>> wrote: >> > >> > >> > >> > In Detail: >> > Say, I read all the data into my vb form from an Oracle table. And I >> > need to know whether it has been updated after that without reading >> > the same data again. >> > >> > >> > >> > >> > >> > >> > >> > > >> >> >> > > > -- > Warm Regards, > Latha. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Oracle PL/SQL" group. To post to this group, send email to Oracle-PLSQL@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Oracle-PLSQL?hl=en -~----------~----~----~----~------~----~------~--~---
