Greetings - I have worked with Oracle for many years and it appears that SAPDB has inherited this horrible datatype. I submit that either a simple API should be provided for this nasty construct so that it can be used relationally, or else it should be obsoleted (as Oracle is doing) in favor of an API to a protected filesystem based data entity that can be indexed and incorporated in a relational schema - e.g. a CLOB or BLOB datatype.
As an additional comment, when I first started working with Oracle, I used LONG datatypes to manage various data. Then I got exposure to the *real* world and found that high performance applications used native filesystem based storage with surrogate relational pointers as DB objects. Let's consider evolving SAPDB to use the more flexible CLOB and BLOB datatypes. SAPDB is a wonderful platform. Let's improve it instead of constantly arguing about workarounds. J.E. Lieberman (SAPDB user and fan) --- [EMAIL PROTECTED] wrote: > Send sapdb.general mailing list submissions to > [EMAIL PROTECTED] > > To subscribe or unsubscribe via the World Wide Web, > visit > > http://listserv.sap.com/mailman/listinfo/sapdb.general > or, via email, send a message with subject or body > 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it > is more specific > than "Re: Contents of sapdb.general digest..." > > > Today's Topics: > > 1. RE: Problem with Selecting value of LONG data > type column on WebPage ADO/ASP on IIS/WIN2k (Carl > Olivier) > > --__--__-- > > Message: 1 > Reply-To: <[EMAIL PROTECTED]> > From: "Carl Olivier" <[EMAIL PROTECTED]> > To: "Zabach, Elke" <[EMAIL PROTECTED]>, > "'Markus Gieppner'" <[EMAIL PROTECTED]>, > "Koetter, Thomas Theodor" > <[EMAIL PROTECTED]>, > "'Srdjan Josipovic'" <[EMAIL PROTECTED]>, > <[EMAIL PROTECTED]> > Subject: RE: Problem with Selecting value of LONG > data type column on WebPage ADO/ASP on IIS/WIN2k > Date: Wed, 22 May 2002 11:18:26 +0200 > > Hi Elke. > > I understand ( not as well as you do ) that there is > a fair amount of > difficulty involved in providing the feature we are > asking afer. > > However from our side, a purely implementation > perspective, the following > example may assist in my needs from a functional > level: > > When we do a keyword search in content stored in our > DB (SAPDB) it would be > great to be able to utilise a feature such as is > available in MS SQL Server > (using the LIKE predicate and the % wildcard) as > follows: > > select id from content where content like > "%mykeyword%" > > obviously this is in the case where the colum > content is a LONG.... > The % wildcard would be chars on that side of any > value(s) and vise versa > (as in pre- and -post) > > Anyway, hope that helps! > > Regards, > > Carl > > -----Original Message----- > From: Zabach, Elke [mailto:[EMAIL PROTECTED]] > Sent: 22 May 2002 10:59 > To: '[EMAIL PROTECTED]'; 'Markus Gieppner'; > Koetter, Thomas Theodor; > 'Srdjan Josipovic'; [EMAIL PROTECTED] > Subject: RE: Problem with Selecting value of LONG > data type column on > WebPage ADO/ASP on IIS/WIN2k > > > Hi, > > after some discussions internally now the question > to the whole list: > > LONG-columns cannot be used in WHERE-condition > (except for IS > NULL-qualification). > Some people ask for LIKE in LONGs or ask for '=' for > LONGs. > > Do you really want LONG columns to be checked for > LIKE (longcol LIKE > 'abc*def', the star standing for 1.4325GB or so?) > or do you need some longer character values, may be > up to 64 KB? > > We here cannot imagine unformatted text with a > length of more than > (let's say) 64KB. > > Let us think of WORD-docs, but they are not > unformatted and therefore > comparing will usually > not return the wanted result. > > It is easy to ask for this feature. It is not that > easy to implement it. And > therefore we would like > to know what you need. What you need, not what is > easy to write down without > thinking about > the usage, performance, ... > > Thank you > > Elke > SAP Labs Berlin > > > -----Original Message----- > > From: Carl Olivier [mailto:[EMAIL PROTECTED]] > > Sent: Mittwoch, 22. Mai 2002 08:14 > > To: Zabach, Elke; 'Markus Gieppner'; Koetter, > Thomas Theodor; 'Srdjan > > Josipovic'; [EMAIL PROTECTED] > > Subject: RE: Problem with Selecting value of LONG > data type column on > > WebPage ADO/ASP on IIS/WIN2k > > > > > > Hmm. > > > > Seems like a slight oversight that! We have had > to do major > > work-arounds > > the LONG datatype for many different applications > in code, > > which obviously > > causes performance issues. > > > > Is there no way that you could look at > prioritising this > > slightly higher > > than it seems to be at the moment? Having to used > Prepared > > Statements in > > updates in tables where there are LONG columns is > cumbersome > > in smallish > > level applications, but the major problem is not > being able > > to compare LONG > > columns or use the LIKE predicate... > > > > Anyway, my 2 cents, use it, don;t use it, I leave > it with you ;) > > > > Regards, > > > > Carl > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On > Behalf Of Zabach, Elke > > Sent: 22 May 2002 07:57 > > To: 'Markus Gieppner'; Koetter, Thomas Theodor; > 'Srdjan Josipovic'; > > [EMAIL PROTECTED] > > Subject: RE: Problem with Selecting value of LONG > data type column on > > WebPage ADO/ASP on IIS/WIN2k > > > > > > Markus Gieppner wrote: > > > > > > > "in SAP DB you cannot use long columns like > "usual" ones in a where > > clause." > > > > > > Is this (even in a very basic/simple/limited > form) planned > > for a future > > release? > > > > > > This is not planned in a foreseeable release > > > > Elke > > SAP Labs Berlin > > > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > === message truncated === __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
