[Logo]
Forums Register Login
What is your view on my design ? - very urgent
All,
I need to write a back-end module(import feature)which receives XML data containing entire data dump(around 10,000 records)and same shall be updated into database. Updating database involves insert/update/delete records in 10 tables. Import need to be done every night(off peak hour). My design is as follows,

1. Write 10 CMPs for 10 tables
2. Relate CMPs using CMR
3. Use Local Interfaces to improve performance

Since lot of things are changed in CMP2.0, I feel performance will NOT be an issue with CMP.

What do you feel? This is very urgent, please provide your comments at the earliest.

~Prasanna
----------
What are you currently using for accessing those 10 tables? Whatever it is, I would probably go with the same technique because A) you'll probably be able to reuse a lot of code and B) you won't confuse the other code's caching etc.
I suspect I don't understand the problem. If you are just inserting records why not use prepared statements and JDBC?
10,000 rows , if CMP is used I feel it is not a good approach. For updating a row, I need to call the finder methods and then update it the retrieved enity reference.
I feel that simple JDBC will do.
10,000 records with CMP isn't that bad when talking about a once-a-night type of batch with no real-time requirements. Anyway, if the main application is reading those tables through a CMP layer, it won't see changes made directly into the database using JDBC.
Thanx for your response.
For my module performance is a very big criteria. I do not want to take any risk. Can I go ahead with CMPs or shall I start writing BMPs?.
My thought is that using CMP2.0 local interfaces is as good as using just a JDBC, with the advantage of having wrapper over JDBC.
Once again thanx for your response.
-------------------
 
My thought is that using CMP2.0 local interfaces is as good as using just a JDBC, with the advantage of having wrapper over JDBC.

CMP with local interfaces is still not exactly JDBC -- CMP has it's pros and cons over it. JDBC is by far the most efficient way to do things, performance-wise, but CMP would protect you from clashes between data inserted through a "back door" and a CMP caching layer not being aware of these insertions.
Wink, wink, nudge, nudge, say no more ... https://richsoil.com/cards



All times above are in ranch (not your local) time.
The current ranch time is
Nov 17, 2017 20:09:43.