Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Abu Yahya Newsgroups: comp.lang.java.programmer,comp.programming,comp.lang.java.databases Subject: Re: Storing large strings for future equality checks Date: Wed, 08 Jun 2011 23:49:00 +0530 Organization: Aioe.org NNTP Server Lines: 16 Message-ID: References: NNTP-Posting-Host: LePVoNEtezBuiMA9+cM5gA.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 X-Notice: Filtered by postfilter v. 0.8.2 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:5126 comp.programming:443 comp.lang.java.databases:465 On 6/8/2011 10:28 PM, David Kerber wrote: > [This followup was posted to comp.lang.java.databases and a copy was > sent to the cited author.] > > 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. Thanks - simply storing them the way they are does seem to be the best way forward.