Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!samsung!aplcen!haven!vrdxhq!dev!jkrueger From: jkrueger@dev.dtic.dla.mil (Jonathan Krueger) Newsgroups: comp.databases Subject: Re: variable record length Keywords: RDBMS, variable record length Message-ID: <3605@dev.dtic.dla.mil> Date: 7 Feb 90 15:38:12 GMT References: <4qx80zz@unify.uucp> Organization: Defense Technical Information Center (DTIC), Alexandria VA Lines: 30 craig@unify.uucp (Craig Isaacs) writes: >With variable width columns (UNIFY's "text" and "binary" field types) >customers can store images, documents, etc... as part of their >RDBMS so they can integrate their RDBMS applications with other >technologies. Oh, good. Please tell us how UNIFY selects on columns of this type. For instance, take the document idea, say given a table like +-----+ | emp | name hiredate resume +-----+---------+-------------------------------------------------+ | Stevans | 20 Sept 1989 | 1975 to 1978: wrote database ... | +---------+-------------------------------------------------+ would the select syntax look like select name from emp where fulltext(resume, "UNIX") = 1 Or what would it look like? Also, please explain how indexing and storage structures would prevent exhaustive table scans. This will help us understand how UNIFY customers can integrate their RDBMS applications with other technologies. -- Jon -- Jonathan Krueger jkrueger.dtic.dla.mil uunet!dgis!jkrueger Isn't it interesting that the first thing you do with your color bitmapped window system on a network is emulate an ASR33?