home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!munnari.oz.au!bruce.cs.monash.edu.au!goanna!escargot!arthur
- From: arthur@otto.bf.rmit.oz.au (Arthur Adamopoulos)
- Newsgroups: comp.databases
- Subject: Re: data dictionaries
- Summary: PICK dictionaries
- Message-ID: <19504sINNd5t@escargot.xx.rmit.OZ.AU>
- Date: 15 Sep 92 15:40:12 GMT
- References: <BuM69C.ny@cs.vu.nl>
- Organization: RMIT Computer Centre
- Lines: 29
- NNTP-Posting-Host: otto.bf.rmit.oz.au
-
- In article <BuM69C.ny@cs.vu.nl>, jfmburg@cs.vu.nl (JFM Burg) writes:
- > A few weeks ago their was a discussion going on about a data-dictionary
- > standard. Somebody replied the question "What should a DD contain anyway".
-
- I mostly work with PICK like systems.
- Pick has no real data definition language, all the DDL stuff is done
- inside the PICK dictionaries.
-
- These can define:
- Usual Field Number, Column Heading, Length and Type.
- Output format - ie. all formats for dates, money values, times etc.
- Input checks - patterns, lengths, ranges etc etc
- Correlatives - Calculation fields.
- - This is the power of pick. You can define almost
- any calculation on fields in the current file and get
- data from other files(tables).
- Program Code - Some versions of pick allow full code in the dicts
- (for calculations, input checks etc).
-
- In my limited use of Oracle I have seen some similar features but then
- I haven't fully explored it yet.....
-
- -----------------------------------------------------------------------
- Arthur Adamopoulos ACSnet: arthur@otto.bf.rmit.oz
- Business Info Systems Internet: arthur@rmit.edu.au
- RMIT
- 411 Swanston st. Tel: +61 03 660 3501
- Melbourne 3000 ICBM: 37 48 S / 147 58 E
- -----------------------------------------------------------------------
-