Re: hug a table

Post #156,909 by admin 5/25/04 4:34:59 PM Reply	Re: hug a table It may always be the same format, but the actual values may throw off the parsing unless your reg.ex is perfect. Format: some.string.for.a.key=The value for it. You're inventing problems. Yes, I know you like to write where clauses to search for stuff. It Isn't Necessary. I don't even use regular expressions to grep for things. In fact, this is a stupid conversation to begin with. Here's the search process: What screen? FooScreen. OK, go to the FooScreenMessages.properties file. What language? French. OK, go to the FooScreenMessages_fr.properties file. What message key? "some.error.message". OK, open FooScreenMessages_fr.properties file, hit 'ctrl-s' for search, and start typing the key 'some.error.message'. You're inventing problems. Data-centric shops often are familiar with and accept table browsing tools. I agree that a shop needs a certain level of "investment" in tablized techniques before it is cost effective, but once you reach that point, tables are a very nice thing. We have over 1 million lines of PL/SQL source code. Huge hulking database servers. Hundreds of tables. Millions upon millions of records in them. Everyone here has a copy of Toad, and most of them can use SQLPlus without batting an eye. I hardly think we qualify as unfamiliar with table browsing tools. Storing the same stuff in text files seems archaic in comparison. It's the simplest thing that works. Putting it in tables adds nothing to the process other than overhead. But tables are the wave of the future. Keep telling yourself that. To everyone else they're just one tool among many. So to distill your arguments: use tables instead of text files because Bryce is more familiar with them. Other than that there are no tangible benefits. Since you didn't answer the other points, I will assume that you concede the overhead. Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."*
Post #156,914 by tablizer 5/25/04 5:08:34 PM Reply	query and change by multiple factors Here's the search process: What screen? FooScreen. OK, go to the FooScreenMessages.properties file. What language? French. OK, go to the FooScreenMessages_fr.properties file. What message key? "some.error.message". OK, open FooScreenMessages_fr.properties file, hit 'ctrl-s' for search, and start typing the key 'some.error.message'. Yes, but if you have multiple screens to change, you end up opening and closing a bunch over and over again. Suppose you had a query like: \n select * from messages \n where appID='nerg'\n and screen='blah' and msgKey='zok' and language='french'\n Then you would only have to edit the search parameters for each one. (Some browsers can be made to prompt if you put a special marker in place of a parameter.) There is no open-open-open, close-close-close, open-open-open.... pattern that a file editor would have to keep going through. (Yeah, I know, you can write editor scripts.) And suppose we needed to change the word 'back' to 'previous' in multiple screens: \n select * from messages \n where msgText like '%back%' and language='english'\n We can then get a list, inspect it to see which ones need changing, and then change those we want. (I am assuming that we want to study each one rather than a sudden bulk change.) Your approach would take longer because you have to open and close each file/screen that needs a change. The query brings it all together in one edit-grid. In fact, the query approach will immediatly tell us how many need changing. You would have to go to grep first. ________________ oop.ismad.com
Post #156,916 by drewk 5/25/04 5:15:48 PM Reply	vim `grep -lr "search_term" *` === Implicitly condoning stupidity since 2001.
Post #156,919 by admin 5/25/04 5:19:28 PM Reply	No, no, no! Firing up Toad and running the same query in 6 different environments is MUCH better than doing that! Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."
Post #156,941 by tablizer 5/25/04 6:24:32 PM Reply	grep is your SQL Firing up Toad and running the same query in 6 different environments is MUCH better than doing that! Toad would already be open. So grep and goofy command-line parameters are better? And each utility invents its own. ________________ oop.ismad.com
Post #156,997 by pwhysall 5/26/04 1:02:40 AM Reply	Of course it is :) Because "grep string files" is SO much HARDER than "SELECT stuff FROM tables WHERE string=somevalue ORDER BY something;", innit? Peter [link\|http://www.debian.org\|Shill For Hire] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Blog]
Post #157,004 by tablizer 5/26/04 1:44:31 AM Reply	SQL requires much less parsing because "slots" predefined ________________ oop.ismad.com
Post #156,917 by admin 5/25/04 5:17:54 PM Reply	It doesn't work that way. Shared messages are in one file. And your ignoring the issue of promoting these changes through the environments. Until you understand that, all of this is really hand-waving. You're adding nothing other than overhead. Your approach would take longer because you have to open and close each file/screen that needs a change. It might if that were an actual change that occurred. You're inventing problems. Or let's say you're not. Let's say that someone actually comes up with that change, once. WHO CARES? You're adding overhead and complexity for one lousy change that might happen once. Sounds like a pain in the ass to me. And are you going to concede that we aren't exactly unfamiliar with databases and their uses here? Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."

Welcome to IWETHEY!