Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!feeder.erje.net!newsfeed.straub-nv.de!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!feed.news.schlund.de!schlund.de!news.online.de!not-for-mail From: Lothar Kimmeringer Newsgroups: comp.lang.java.programmer,comp.programming,comp.lang.java.databases Subject: Re: Storing large strings for future equality checks Followup-To: comp.lang.java.programmer Date: Wed, 8 Jun 2011 20:31:39 +0200 Organization: Organization?! Only chaos here! Lines: 24 Message-ID: <19aedpuwexqkx$.dlg@kimmeringer.de> References: Reply-To: news@kimmeringer.de NNTP-Posting-Host: mnch-4d044605.pool.mediaways.net Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: online.de 1307557900 32693 77.4.70.5 (8 Jun 2011 18:31:40 GMT) X-Complaints-To: abuse@einsundeins.com NNTP-Posting-Date: Wed, 8 Jun 2011 18:31:40 +0000 (UTC) User-Agent: 40tude_Dialog/2.0.15.1de Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:5130 comp.programming:446 comp.lang.java.databases:468 David Kerber wrote: > In article , abu_yahya@invalid.com > says... >> >> A small application that I'm making requires me to store very long >> strings (>1000 characters) in a database. > > Unless you're storing millions of these strings or using Access, I'd say > just store and use the string. I think you'll find that the speed > penalty is nearly unnoticeable. Depends on the database. Some of them force you to use CLOBS for text-columns with more than 255 characters. CLOBS are a PITA in terms of indexing. Regards, Lothar -- Lothar Kimmeringer E-Mail: spamfang@kimmeringer.de PGP-encrypted mails preferred (Key-ID: 0x8BC3CD81) Always remember: The answer is forty-two, there can only be wrong questions!