I am considering returning JSON from a user-defined function and wondering if the idea has merit.
The database would be in server mode and rather than have the client application perform the select and iterate through the resultset; I am wondering if it would be faster for a user-defined function to perform the select, iterate through and return the JSON. The resulting JSON would be typically 40 to 120k in size containing 'list' type data. When a client iterates through the resultset, how is the data moved from the H2 server to the app ? (what size chunks ?) What would be the appropriate output datatype to use to return the JSON? If clob would that result in further disk writes before being sent to the client ? Thinking about potentially storing the processed JSON in another table and using triggers to update it when required. Any words of wisdom are appreciated! -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
