Hi! On Thursday, February 14, 2013 3:55:39 PM UTC+1, Mario Camou wrote:
> We're actually thinking of implementing a PostgreSQL HSTORE-based > storage...Have you considered this? It "might be" similar to the existing > REDIS-based storage. > We've considered that - but it doesn't make much sense :-). The main advantage of hstore is to be able to index and query over the unstructured metadata, and this is not required by the ruote engine, that needs only the wfid to fetch the metadata. If you were using hstore, you would have anyway to convert from the JSON representation used by ruote to the hstore text representation; moreover, you'd only be able to have strings both as keys and values, that is all that hstore supports. If one metadata value needs to be, say, an Array or an Hash, you'll end up serializing that value in JSON and storing it in hstore. Yuck! :-) On the other hand, the JSON[1] data type, available since PostgreSQL 9.2, is a perfect fit for this task: PG only checks whether the JSON is well-formed before storing it. So, I think that an improvement of ruote-postgres would be to use a json column if running on 9.2 or higher, and a text column for previous versions. Thanks for the feedback! :-) ~Marcello [1]: http://www.postgresql.org/docs/9.2/static/datatype-json.html -- -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en --- You received this message because you are subscribed to the Google Groups "ruote" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
