T
Thomas Mercer-Hursh
Guest
OK, Julian, that is the first indication I have seen of an actual benefit. Now, to convince PSC development, what is the use case? The use case I get for stuffing JSON into a DB is things like preserving context across sessions. I can see wanting to index that by session id and the like, maybe a timeout value for when to preserve it, etc., but I would put those in separate fields. What are you doing with these JSON objects that you would want to retrieve on key-value pairs? Seems to me that implementing such a search feature would actually involve greater difficulty than allowing word search on a CLOB. Couldn't one accomplish this with word index? Mike, you are right, I am not getting the point. I understand use cases for putting JSON data into a database for things like caching it across passes on an AppServrer, but no, I don't know what the use case is for 100,000 of them and wanting to search across it. If one is storing a large amount of data and wanting index capabilities, why would one not put the data into regular fields? I am not against you, just playing Doubting Thomas in making you present an actual use case like development would need before considering such a thing.
Continue reading...
Continue reading...