Hi guys, I'm working on it. Best Regards,
Luca Garulli CEO at Orient Technologies LTD the Company behind OrientDB http://about.me/luca.garulli On 21 May 2015 at 10:59, Fabrizio Fortino <[email protected]> wrote: > https://github.com/orientechnologies/orientdb/issues/2312 > > > On Monday, May 18, 2015 at 3:04:57 PM UTC+1, Chandima Jayawickrema wrote: >> >> Was an Issue open for this? I still do not see this fixed in v2.0. This >> is a major issue for us and writing wrapper queries has become complex in >> some of our dynamic queries. >> >> regards, >> Chandima >> >> On Friday, May 2, 2014 at 11:17:28 PM UTC+5:30, Lvc@ wrote: >>> >>> Hi Fabrizio, >>> You're right: now NULL are excluded. May you open a new issue? >>> >>> In the meanwhile the Hung's roundtrip could help. >>> >>> Lvc@ >>> >>> >>> On 2 May 2014 10:37, Fabrizio Fortino <[email protected]> wrote: >>> >>>> I see your point but I still think GROUP BY should consider null >>>> values. I have tested the same queries on Oracle and SQL Server and both >>>> consider null values on GROUP BY. >>>> >>>> Cheers, >>>> Fabrizio >>>> >>>> >>>> On Friday, May 2, 2014 7:28:07 AM UTC+1, Hung Tran wrote: >>>>> >>>>> Hi, >>>>> >>>>> I don't think so, Null is an undefined value, A Null value will never >>>>> equal to any other Null values. If you consider all NULL values are the >>>>> same, you need to alias them by empty string (*ifnull*() may help you >>>>> in your case), or something special. >>>>> >>>>> My Best, >>>>> Hung Tran >>>>> >>>>> On Friday, May 2, 2014 6:39:33 AM UTC+7, Fabrizio Fortino wrote: >>>>>> >>>>>> Hi there, >>>>>> >>>>>> I have a class that looks like this >>>>>> >>>>>> CODE,PRIORITY >>>>>> 0001,HIGH >>>>>> 0001,LOW >>>>>> 0001,LOW >>>>>> 0002,HIGH >>>>>> <null>,HIGH >>>>>> >>>>>> Executing the following query >>>>>> >>>>>> select CODE, count(*) as count group by (CODE) >>>>>> >>>>>> I get >>>>>> >>>>>> CODE,count >>>>>> 0001,3 >>>>>> 0002,1 >>>>>> >>>>>> Executing a multi group by select >>>>>> >>>>>> select CODE, PRIORITY, count(*) as count group by (CODE, PRIORITY) >>>>>> >>>>>> I get >>>>>> >>>>>> CODE,PRIORITY,count >>>>>> 0001,HIGH,1 >>>>>> 0001,LOW,2 >>>>>> 0002,HIGH,1 >>>>>> <null>,HIGH,1 >>>>>> >>>>>> In my opinion, the first query should return a result for the <null> >>>>>> group >>>>>> >>>>>> CODE,count >>>>>> 0001,3 >>>>>> 0002,1 >>>>>> <null>,1 >>>>>> >>>>>> >>>>>> WDYT? Should I open an issue on this? >>>>>> >>>>>> Thanks, >>>>>> Fabrizio >>>>>> >>>>>> >>>>>> >>>>>> -- >>>> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "OrientDB" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
