|
Richard D. Dettinger wrote: Perhaps it seems like a "baby with the bathwater" solution, and perhaps for your situation (and many others) it is. ----------- Actually, I don't have a situation, per se. I'm a teacher. But my primary goal these days is to get people up and running on thin client technology with the minimum possible disruption to their legacy systems. But a secondary goal is to provide single-box e-business solutions; for that, I can definitely use the unicode approach. It's simply a matter of which solution is needed. But our goal (meaning my team, not IBM's - I do not speak on behalf of IBM) is to provide the solutions that make JDBC as fast as it can be. Many of the customers we work with regularly are buying boxes only to run Java/JDBC/Websites. Others are willing to have two full copies of their data (one in the traditional CCSID and one in unicode). This can make sense when you have a table of reasonable size which is pretty stable but that can get queried constantly (a product table for many companies). ----------- In a hybrid situation such as the one you mention, I think it makes perfect sense to go with a ghost table, perhaps maintained by a trigger on the primary. I'm not against any particular method (although if you've read anything I've written, you might get the - correct - impression that I don't advocate JDBC for transaction processing, for a whole host of reasons). Clearly everyone has different needs. ----------- Yes indeed. And as a teacher, I need ALL of them <laughing>. Thanks very much for the input, Richard. +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.