Pass struct as result value? about machinery HOT 3 CLOSED

Structs are difficult as all return values must be JSON serializable. Maps might be easier to support but only restricted to maps that can be represented as a valid JSON object. So the implementation might be a bit trickier.

from machinery.

Actually what I can do is just serialize the structs I need into strings manually myself using the encoding/json package for the time being. It seems similar questions are asked with Redis and the response is to serialize manually. http://stackoverflow.com/questions/27468458/go-how-to-save-and-retrieve-a-struct-to-redis-using-redigo

from machinery.

This sounds like a bad design. Any tasks exposed via machinery should be quite simple and complex logic (methods that return, accept structs) should be private and called from the simple exposed public tasks.

What I would probably do is have some sort of a Result struct, which has a corresponding table in your database. Just return the primary ID of result object. And then whatever code where you are handling result values should just take the primary key and fetch the object from the database.

I would suggest something similar for input arguments, just passing primary keys as arguments and fetching from database / creating structs inside the function. This should keep the public API clean and simple. Bulk of the business logic can be inside private functions / methods.

from machinery.