On Feb 6, 2014, at 12:57 PM, Gavin Flower wrote:
> On 07/02/14 05:43, Michael Sacket wrote:
>> On Feb 6, 2014, at 2:23 AM, Vik Fearing wrote:
>>
>>> On 02/06/2014 04:16 AM, Michael Sacket wrote:
Often times I find it necessary to work with table rows in a specific,
generally user-supp
On 02/06/2014 11:57 AM, Gavin Flower wrote:
On 07/02/14 05:43, Michael Sacket wrote:
On Feb 6, 2014, at 2:23 AM, Vik Fearing wrote:
On 02/06/2014 04:16 AM, Michael Sacket wrote:
Often times I find it necessary to work with table rows in a
specific, generally user-supplied order. It could be
On 07/02/14 05:43, Michael Sacket wrote:
On Feb 6, 2014, at 2:23 AM, Vik Fearing wrote:
On 02/06/2014 04:16 AM, Michael Sacket wrote:
Often times I find it necessary to work with table rows in a specific,
generally user-supplied order. It could be anything really that requires an
ordering t
On Feb 6, 2014, at 2:23 AM, Vik Fearing wrote:
> On 02/06/2014 04:16 AM, Michael Sacket wrote:
>> Often times I find it necessary to work with table rows in a specific,
>> generally user-supplied order. It could be anything really that requires an
>> ordering that can't come from a natural col
On Wed, Feb 5, 2014 at 7:16 PM, Michael Sacket wrote:
> Often times I find it necessary to work with table rows in a specific,
> generally user-supplied order. It could be anything really that requires an
> ordering that can't come from a natural column. Most of the time this
> involved manipula
Ok, thanks ^^
Cheers,
Rémi-C
2014-02-06 Vik Fearing :
> On 02/06/2014 10:00 AM, Rémi Cura wrote:
> > Hey,
> > I don"t understand the difference between this ORDINALITY option and
> > adding a "row_number() over()" in the SELECT.
>
> WITH ORDINALITY will give you something to order by. You sho
On 02/06/2014 10:00 AM, Rémi Cura wrote:
> Hey,
> I don"t understand the difference between this ORDINALITY option and
> adding a "row_number() over()" in the SELECT.
WITH ORDINALITY will give you something to order by. You should never
do "row_number() over ()" because that will give you potent
Hey,
I don"t understand the difference between this ORDINALITY option and
adding a "row_number() over()" in the SELECT.
Thanks,
Cheers,
Remi-C
2014-02-06 Vik Fearing :
> On 02/06/2014 04:16 AM, Michael Sacket wrote:
>
> Often times I find it necessary to work with table rows in a specific,
>
On 02/06/2014 04:16 AM, Michael Sacket wrote:
> Often times I find it necessary to work with table rows in a specific,
> generally user-supplied order. It could be anything really that
> requires an ordering that can't come from a natural column. Most of
> the time this involved manipulating a po
