Return-Path: Delivered-To: apmail-jakarta-struts-user-archive@apache.org Received: (qmail 35964 invoked from network); 29 Aug 2002 20:29:51 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 29 Aug 2002 20:29:51 -0000 Received: (qmail 6641 invoked by uid 97); 29 Aug 2002 20:17:21 -0000 Delivered-To: qmlist-jakarta-archive-struts-user@jakarta.apache.org Received: (qmail 6598 invoked by uid 97); 29 Aug 2002 20:17:21 -0000 Mailing-List: contact struts-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Struts Users Mailing List" Reply-To: "Struts Users Mailing List" Delivered-To: mailing list struts-user@jakarta.apache.org Received: (qmail 6572 invoked by uid 98); 29 Aug 2002 20:17:20 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Date: Thu, 29 Aug 2002 13:16:43 -0700 (PDT) From: "Craig R. McClanahan" To: Struts Users Mailing List Subject: RE: [New Functionality] ApplicationResources.properties to DB? In-Reply-To: Message-ID: <20020829131443.Y50464-100000@icarus.apache.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Thu, 29 Aug 2002, Ian Vellosa wrote: > Date: Thu, 29 Aug 2002 21:54:10 +0200 > From: Ian Vellosa > Reply-To: Struts Users Mailing List > To: Struts Users Mailing List > Subject: RE: [New Functionality] ApplicationResources.properties to DB? > > But what do you do each time you add a new language, say German? you need to > update the database structure adding a new column? Surely any solution > should be generic enough not to need that. > > Unfortunately you would need the table to look something more like: > > key language value > ------------ -------- ---------------- > global.title en Something > global.title fr quelque chose > > but that will get huge in no time at all! and I doubt that performance would > be too good. > Performance shouldn't be an issue if you index on both key and language. Don't forget to implement the inheritance rules for Locales, such that if the user's Locale is "en_US" you search for language="en_US", then language="en", then the default. Craig > > -----Original Message----- > From: James Mitchell [mailto:jmitchtx@telocity.com] > > > -----Original Message----- > > From: Eddie Bush [mailto:ekbush@swbell.net] > > > > James Mitchell wrote: > > > > >Sorry guys... for not responding earlier. > > > > > > > > > Sorry I should have filled you in, James. I forwarded him the relevant > > part of your discussion. > > > > >Also, I'm not sure how many passes I would make over the list, > > you certainly > > >wouldn't want a circular reference. > > > > > > > > > Since we're talking about a database here: > > > > Yes, you'd want to avoid circular references. However, I wouldn't think > > it would take more than a single pass through the view to churn out all > > of your resources. If you used the key as ... *drum roll* ... the key, > > you could just look it up out of the database. That's just my initial > > impression ... > > Well, I was thinking something more abstract. You shouldn't rely on being > able to have a key (in the JDBC sense). After all, the storage might be a > single table like this: > > key en en_US fr > --------- ------- ---------- -------------- > global.title Something (null) quelque chose > > > ...or it could be a very complicated structure based off of a "previously > data driven ASP site" with a simple view giving you your info. > > > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > -- To unsubscribe, e-mail: For additional commands, e-mail: