Phalcon 2.0 PHQL Distinct

Question

Phalcon 2.0 PHQL Distinct

Alex Nunes Dec '14

Created Dec '14	Last Reply Jan '15	Replies 2	Views 927	Votes 0

Alex Nunes 1.9k

Dec '14

Hey,

I was checking out 2.0 and one of my PHQL queres uses distinct. It works fine in 1.3.4 but omits the column in 2.0. I was wondering if anybody knows if this is known issue or if there is newer syntax for using distinct in PHQL?

Dylan Anderson · Answer 1 · 2014-12-08T15:37:09-07:00

2.0 is supposed to have 100% feature parity with the 1.x branch. If you can distill this down to a simple example case, it would make a good bug report.

Alex Nunes · Answer 2 · 2014-12-09T07:49:35-07:00

Essentially a statement such as:

SELECT DISTINCT value FROM model JOIN etc.

This won't return "value" in 2.0 but returns fine in 1.3.4 when using PHQL.

Michael Markey · Answer 3 · 2015-01-22T01:14:05-07:00

Alex, did you find a solution? I think I might have a similar situation here:

$query = $this->modelsManager->createQuery('SELECT DISTINCT id, name FROM App\Models\Brands');
$result = $query->execute();

Dumping the returned result shows the following. It seems that the first column is returned as "_0", regardless of the column. (Switching the order of name and id still returned the first column as "_0".

[_pdoStatement:protected] => PDOStatement Object
(
[queryString] => SELECT DISTINCT brands.id AS _0, brands.name AS name FROM brands
)
[_sqlStatement:protected] => SELECT DISTINCT brands.id AS _0, brands.name AS name FROM brands