Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!dev!dgis!jkrueger From: jkrueger@dgis.dtic.dla.mil (Jon) Newsgroups: comp.databases Subject: Re: text and binary fields (columns) Keywords: RDBMS, variable record length Message-ID: <765@dgis.dtic.dla.mil> Date: 19 Feb 90 21:26:52 GMT References: <4qx80zz@unify.uucp> >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 ... >>Our syntax would look like: >> SELECT name FROM emp WHERE resume LIKE '%UNIX%'; Craig, all commercially available RDBMS engines perform pattern matching on strings. Where exactly does Unify's product add value? >Actually, you could create indicies (indexes) on the text field; however, we >are not in the business of creating full text retrieval packages (and therefore >do not optimize for full text retrieval). "Do not optimize" is a polite way of saying "do not implement", isn't it? If not, please explain how you will avoid exhaustive table scan. >The *technology* is there, however, so you *can* integrate with other >technologies like full text retrieval and scanned images. What technology is where, Craig? What part has Unify supplied? What does it make possible that any RDBMS doesn't? -- Jon -- Jonathan Krueger jkrueger@dtic.dla.mil uunet!dgis!jkrueger The Philip Morris Companies, Inc: without question the strongest and best argument for an anti-flag-waving amendment.