Title: RE: [jdjlist] Re: String List Compare
Just finished it! Actually, aside from the dreadfull-looking SQL, it's quite fast. Only 1.85 seconds!
 
Thanks again, this is one happy camper!
 
Greg Nudelman
-----Original Message-----
From: Armando Valenzuela [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 26, 2003 5:40 PM
To: jdjlist
Subject: [jdjlist] Re: String List Compare

Hi..
You can try  (if you can) by changing your DB structure making a N-N table (relational) ,  { key of table x , key of table states  }. and make a db index of  key-state in the N-N table, and the respective query..
 
 
 
 
----- Original Message -----
To: jdjlist
Sent: Wednesday, March 26, 2003 3:13 PM
Subject: [jdjlist] Re: String List Compare

Dear DR, sorry but I can't give you any details, and here is why:

1) The one reason for the predicament is that legacy DB structure is horrible, and this query will be 2 pages long, and not likely to EVER come up again (I sincerely hope others do not have the same to deal with!!) 

2) Explanation will take 2-3 pages, time I do not have.
3) I'm still coding the solution!!!
4) I can't reveal the particulars of the IMX internal DB structure... do you want the Lawyers after both of us??!!

:-)

But seriously, the point was that using the SQL LIKE *is* the solution here.  As long as you can bypass any String operations in Java and twist and turn your (even VERY, VERY, VERY badly designed) legacy table structure around so you can somehow (self-join, union, group by N different columns together, etc.) do it in the SQL in the DB, you're way way ahead of any Java solution.  That is the take-home lesson here.

But if you have some kind of tricky problem YOU are working on, post away, I'd love to have a crack at it!

Cheers!

Greg

-----Original Message-----
From: David Rosenstrauch [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 26, 2003 2:49 PM
To: jdjlist
Subject: [jdjlist] Re: String List Compare


On Wednesday 26 March 2003 04:05 pm, you wrote:
> Fortunately, not all of the 45000 are used every time, and then not all
> of them are the list... Anyway, no more worries!! I just had a very
> intense brainstorming session with our group and we came up with an
> awsome way to use the SQL LIKE '%CA%' -- this is going to be SUPERFAST.
> No Java String operation will be able to touch this new SQL, ever.
>
> Thanks to all who pitched in.
>
> :->
>
> Greg


What?  Rope us all in, throw out the teaser of a super-fast solution, and then
leave us hanging?!?!?!?   :-)

Please do share your solution with the list!


Curiously yours,

DR


---
You are currently subscribed to jdjlist as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
http://www.sys-con.com/fusetalk

---
You are currently subscribed to jdjlist as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
http://www.sys-con.com/fusetalk
---
You are currently subscribed to jdjlist as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
http://www.sys-con.com/fusetalk
---
You are currently subscribed to jdjlist as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
http://www.sys-con.com/fusetalk

Reply via email to