Super awesome... This solves my varying nested level polymorphic nightmare. It took me a while to sort this out, but after a few synapse cycles it finally makes sense. Thanks!
I had to run unicorn as the web server with multiple workers, I couldn't get pow to serve the pdf even if I changed the number of workers pow was using.
Implementing the roll your own method of this for a project of mine and I keep getting an error when I attempt to find all "draft" or "open" or "whatever" orders:
ERROR: column "orders.id" must appear in the GROUP BY clause or be used in an aggregate function
LINE 1: SELECT "orders".* FROM "orders" INNER JOIN "order_events" ON...
Thanks!!!
Super awesome... This solves my varying nested level polymorphic nightmare. It took me a while to sort this out, but after a few synapse cycles it finally makes sense. Thanks!
I had to run unicorn as the web server with multiple workers, I couldn't get pow to serve the pdf even if I changed the number of workers pow was using.
I just removed the grouping and it works fine, not sure what purpose the group("order_id") was serving, maybe I am missing something?
Implementing the roll your own method of this for a project of mine and I keep getting an error when I attempt to find all "draft" or "open" or "whatever" orders:
ERROR: column "orders.id" must appear in the GROUP BY clause or be used in an aggregate function
LINE 1: SELECT "orders".* FROM "orders" INNER JOIN "order_events" ON...
Any ideas?
Any luck with this?
What about using a different column than "slug", I see some reference to setting configuration options in the documentation, but I have no idea how.
Any tips on getting hstore to work on Linode following these directions? I am seeing:
PG::Error: ERROR: could not open extension control file "/usr/share/postgresql/9.1/extension/hstore.control": No such file or directory
+1
What about creating a user via the console? I can't find any methods for creating the password_digest.