home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!europa.asd.contel.com!emory!sol.ctr.columbia.edu!news.unomaha.edu!news.mtholyoke.edu!nic.umass.edu!titan.ucc.umass.edu!dtodd
- From: dtodd@titan.ucc.umass.edu (David M. Todd)
- Newsgroups: comp.databases
- Subject: Changes in Advanced Revelation from 1.16 to 3.0
- Message-ID: <BxJyoE.5uz@nic.umass.edu>
- Date: 11 Nov 92 12:57:50 GMT
- Sender: usenet@nic.umass.edu (USENET News System)
- Organization: University of Massachusetts, Amherst
- Lines: 60
-
-
- Mike Stramba asked me the following in response to my posting
- mentioning that I had just upgraded from Revelation 1.16 to 3.0. I
- thought I'd post my response on Comp.databases to see if others have
- any comments:
-
- > I've still got 1.10 !
- >
- > What are some of the differences, good and bad that have impressed you with
- > the latest version?
- >
- > What, if any functions, commands have been added on the 'user level' e.g.
- > 'LIST' command or R-Basic level for manipulating dynamic arrays?
- >
-
- POSITIVE:
-
- + can control case sensitivity (since 2.??)
-
- + improved menu structure, organization of commands
-
- + mouse capability (since 2.??, but much more fully implemented in
- 3.0) PAINT has been improved and works very well with the mouse.
-
- + manuals are more efficiently organized.
-
- + the tutorial is much improved
-
- + improved functionality and efficiency (e.g. messages are less
- complicated to invoke in code. I'm not thinking of other examples
- right now, but this is my general impressions).
-
- + There are a variety of other improvements that may or may not be
- relevant to you, but they certainly improve the overall standing of
- ARev in the marketplace: SQL query-by-example; environmental bonding
- options; international language options.
-
- ? Some query operations are supposed to be faster, but it is unclear
- how much this affects overall operation. My general impression is
- that 3.0 is slower than 1.16 in genearl use, but I'm still changing my
- code to avoid some translation processes that slow operation (see next
- point).
-
- - The conversion process is tough, primarily because RTI decided to
- enforce SQL standards for table and column naming (underscores are the
- only "punctuation" that can be used). The tradeup process carries out
- the most elemental conversions (changing table names and column
- names), but it doesn't touch code (including dictionaries) or VOC
- rows. ARev tries to translate periods to underscors on the fly, but
- this doesn't work when indexes are involved (e.g. select statements
- using indexed columns). Quite a few people seem to be saying they are
- eager to use 3.0 on new projects, but not to convert old applications.
- I'm converting an old application and it's been a lot of work but it
- seems worth it.
-
- David
-
- |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ David M. Todd ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
- |Department of Psychology, University of Massachusetts, Amherst, MA 01003 USA|
- |Phone: 413/545-0158 ___ <DTodd@Titan.ucc.UMass.EDU> _____ Fax: 413/545-0996|
-