|
From: <ek...@ba...> - 2003-04-04 15:21:26
|
Which brings me back to my initial request (see below) ... I suppose that since I now have my own version of SqlConfig, I could implement this if I want to w/o affecting the code base ... I just thought that this line was not needed. Final thoughts on this? << Bruce, Is the SqlConfig.setString( ) ever called from anywhere except SqlConfigService? If not, I would like to remove the first line of SqlConfig.setString( ), which is: service.setString(this.getName(), name, value); which gets called from SqlConfigService.getConfig( ) to update the internal hashmap with the value read from the database. To include the line above means that immediately after reading the key/value from the database, it will go back to SqlConfigService and call setString( ), which will delete the same row and then re-insert the row. Agreed? Erik >> To: ek...@ba... cc: Bab...@li... Subject: Re: SqlConfig.setString( ) On Friday 04 April 2003 09:11 am, ek...@ba... wrote: > << > > > which gets called from SqlConfigService.getConfig( ) to update the > > internal hashmap with the value read from the database. To include the > > line above means that immediately after reading the key/value from the > > database, it will go back to SqlConfigService and call setString( ), > > which > > > will delete the same row and then re-insert the row. Agreed? > > Not sure what the problem here is? > > > The problem is that the getConfig() method ... which reads from the > database ... ends up deleting and re-inserting the very row it just read. Yeah - Hack, hack. Its not my proudest achievement. |