Hello. If anybody has a minute, is inserting that many data fields into an oracle row (it's a single table as far as i know) kind of crazy? I can't even imagine the single prepared statement to handle all that. Are there alternatives via jdbc? I've been kind of messing around and I am thinking maybe some kind of incremental load...an initial insert followed by updates...but then the SQL statements get hairy and that adds overhead. I guess my preference is to insert/update entire rows instead of targeting sets of field(s). Thank you very much for reading this. Any input is greatly appreciated. [ July 03, 2007: Message edited by: Tom Griffith ]
Yes, 650 fields in a single row is way too much (to me). I try not to go over 30 really. Your also likely to hit size limits of the database table if those fields are too long. Generally, you split to multiple tables with foreign key constraints in such a situation. I imagine a good bit of normalization would likely help you reduce the size of the data as well.
yeah, i thought it was kinda nuts when i heard it but i wans't sure if tables and inserts/updates to single rows that large were a norm out there. I'll be getting more details about it. thank you. Oh yeah, i apologize about the dupe threads...when i submitted the first one, i recevied a sql error back and i didn't find the post so i typed it again. thank you to all for your input.
Talk sense to a fool and he calls you foolish. -Euripides A foolish tiny ad:
professionally read, modify and write PDF files from Java