Re: QB in 1.7: ordering for join'ed tables

> Hi,

Hi,

We talk about 1.7.x. Right?

> is there a specific (technical) reason why I can add constraints in joined tabels
>
>   $qb->add_constraint(uid.username, =, myname)
>
> but not order about it
>
>   $qb->add_order(uid.username)

You may call it a "bug". Briefly QB is designed that way so constraint is absolutely
QB unaware.

This is changed in 'going to be released soon' 1.8.
However QB itself and some parts of its API requires refactoring, especially
for methods like execute_distinct.
IMO of course.

> Furthermore: Why does an invalid constraint a) invalidate the entire
> querybuilder (yielding no results) *and* b) *not* report it to the user in a
> sensible way? (No, I do not call logging it to the Apache error log sensible in
> this case.)

You mean something more than php's warning or notice?
To make this properly ( not _this works now_ ) we need to make core's error reporting
to avoid midgard-php extension logic hell ( like now ).

> Just for a few more cents about why i'm so frustrated about Midgard these days.

This is the main reason why I want to make 1.8 asap. We can provide some pre 1.9
functionality there ( like good error reporting , ready for OO exceptions ).

Piotras