Groups > comp.lang.java.programmer > #5155

Re: Storing large strings for future equality checks

Path	csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!feeder.news-service.com!ecngs!feeder.ecngs.de!Xl.tags.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!local2.nntp.ams.giganews.com!nntp.brightview.co.uk!news.brightview.co.uk.POSTED!not-for-mail
NNTP-Posting-Date	Thu, 09 Jun 2011 05:44:16 -0500
Date	Thu, 09 Jun 2011 11:44:16 +0100
From	bugbear <bugbear@trim_papermule.co.uk_trim>
User-Agent	Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.19) Gecko/20110429 Fedora/2.0.14-1.fc13 SeaMonkey/2.0.14
MIME-Version	1.0
Newsgroups	comp.lang.java.programmer
Subject	Re: Storing large strings for future equality checks
References	<iso8cm$a80$1@speranza.aioe.org> <MPG.285974489deb29be989729@news.eternal-september.org> <19aedpuwexqkx$.dlg@kimmeringer.de> <95bfpaFgboU1@mid.individual.net>
In-Reply-To	<95bfpaFgboU1@mid.individual.net>
Content-Type	text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding	7bit
Message-ID	<__KdncFXQ4icOW3QnZ2dnUVZ8qednZ2d@brightview.co.uk> (permalink)
Lines	25
X-Usenet-Provider	http://www.giganews.com
X-Trace	sv3-U33TD4dPyyTeTAh8KKVwz1Nai9iTQ5c2pqCMN0Ir66NQnV3507YrDdeVMTwPurZQLgK9lwlzSduGqvE!K8p3pSoyYlEWynD5pMkGpu3tmJEBUPmJ87RRe3i7grS72EFzxWvKKTlz7PcfBmRhqzjKaVTA0+Dw!UBnixYLQ9Qv/ZvrP0iIsUTanbg==
X-Abuse-and-DMCA-Info	Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info	Otherwise we will be unable to process your complaint properly
X-Postfilter	1.3.40
X-Original-Bytes	2066
Xref	x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:5155

Show key headers only | View raw

Harry Tuttle wrote:
> Lothar Kimmeringer, 08.06.2011 20:31:
>> 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.
>
> No serious DBMS requires you to use a CLOB for columns with more than
> 255 characters.
>
> The least flexible "big" name is Oracle, which has a limit of 4000
> bytes. Beyond that a CLOB is needed.
>
> Most others have a much larger limit on VARCHAR columns (32k, 64k, 1GB,
> ...)

Agreed, seconded etc.

To OP; just store the strings as you need, make sure the
column is indexed, and simply query with your input
string in the "obvious" way.

Unless this *proves* to be a catastrophe (which I doubt)...
job done.

   BugBear

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Storing large strings for future equality checks Abu Yahya <abu_yahya@invalid.com> - 2011-06-08 22:05 +0530
  Re: Storing large strings for future equality checks markspace <-@.> - 2011-06-08 09:49 -0700
    Re: Storing large strings for future equality checks Willem <willem@toad.stack.nl> - 2011-06-08 17:28 +0000
      Re: Storing large strings for future equality checks Abu Yahya <abu_yahya@invalid.com> - 2011-06-08 23:45 +0530
    Re: Storing large strings for future equality checks Abu Yahya <abu_yahya@invalid.com> - 2011-06-08 23:45 +0530
  Re: Storing large strings for future equality checks David Kerber <dkerber@WarrenRogersAssociates.invalid> - 2011-06-08 12:58 -0400
    Re: Storing large strings for future equality checks Abu Yahya <abu_yahya@invalid.com> - 2011-06-08 23:49 +0530
    Re: Storing large strings for future equality checks Lothar Kimmeringer <news200709@kimmeringer.de> - 2011-06-08 20:31 +0200
      Re: Storing large strings for future equality checks Harry Tuttle <OTPXDAJCSJVU@spammotel.com> - 2011-06-09 10:50 +0200
        Re: Storing large strings for future equality checks bugbear <bugbear@trim_papermule.co.uk_trim> - 2011-06-09 11:44 +0100
      Re: Storing large strings for future equality checks Harry Tuttle <OTPXDAJCSJVU@spammotel.com> - 2011-06-10 10:15 +0200
  Re: Storing large strings for future equality checks Gene Wirchenko <genew@ocis.net> - 2011-06-08 11:07 -0700
    Re: Storing large strings for future equality checks Abu Yahya <abu_yahya@invalid.com> - 2011-06-08 23:58 +0530
    Re: Storing large strings for future equality checks Hallvard B Furuseth <h.b.furuseth@usit.uio.no> - 2011-06-09 12:38 +0200
    Re: Storing large strings for future equality checks Michael Wojcik <mwojcik@newsguy.com> - 2011-06-09 17:32 -0400
      Re: Storing large strings for future equality checks bugbear <bugbear@trim_papermule.co.uk_trim> - 2011-06-10 10:51 +0100
  Re: Storing large strings for future equality checks Lothar Kimmeringer <news200709@kimmeringer.de> - 2011-06-08 20:28 +0200
    Re: Storing large strings for future equality checks Martin Gregorie <martin@address-in-sig.invalid> - 2011-06-08 22:02 +0000
  Re: Storing large strings for future equality checks rossum <rossum48@coldmail.com> - 2011-06-08 21:38 +0100
  Re: Storing large strings for future equality checks Robert Klemme <shortcutter@googlemail.com> - 2011-06-08 23:20 +0200
  Re: Storing large strings for future equality checks Tom Anderson <twic@urchin.earth.li> - 2011-06-08 23:02 +0100
  Re: Storing large strings for future equality checks Joshua Maurice <joshuamaurice@gmail.com> - 2011-06-09 15:01 -0700

csiph-web