On Tue, Feb 3, 2015 at 9:33 PM, BladeOfLight16
wrote:
> This is why ORMs are bad. They make hard problems *much* harder, and the
> only benefit is that they maybe make easy problems a little quicker. The
> cost/savings is *heavily* skewed toward the cost, since there's no upper
On Mon, Feb 2, 2015 at 1:16 AM, Sam Saffron wrote:
> However, the contortions on the above query make it very un-ORM
> friendly as I would need to define a view for it but would have no
> clean way to pass limits and offsets in.
>
This is why ORMs are bad. They make hard problems *much* harder,
On Fri, Jul 26, 2013 at 6:28 PM, Tom Lane wrote:
>
>
> I think we could do with both more documentation, and better error
> messages for these cases. In the SET-where-you-should-use-ADD case,
> perhaps
>
> ERROR: option "use_remote_estimate" has not been set
> HINT: Use ADD not SET to define a
