I'm still on 1.3.1 but planning to upgrade to 1.4 quite soon.
On Mon, May 14, 2012 at 3:50 PM, akaariai wrote:
> On May 14, 3:29 pm, Jani Tiainen wrote:
> > 14.5.2012 14:50, akaariai kirjoitti:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > > On May 14, 2:37 pm, Jani Tiainen wrote:
> > >> Hi,
On May 14, 3:29 pm, Jani Tiainen wrote:
> 14.5.2012 14:50, akaariai kirjoitti:
>
>
>
>
>
>
>
>
>
>
>
> > On May 14, 2:37 pm, Jani Tiainen wrote:
> >> Hi,
>
> >> I have in my database quite a bunch of a models where I do have quite
> >> large fields and I'm using .only('pk', 'identifier') to fetch
14.5.2012 14:50, akaariai kirjoitti:
On May 14, 2:37 pm, Jani Tiainen wrote:
Hi,
I have in my database quite a bunch of a models where I do have quite
large fields and I'm using .only('pk', 'identifier') to fetch only those
two fields - mainly to make serverside natural sort for a data. Data
On May 14, 2:37 pm, Jani Tiainen wrote:
> Hi,
>
> I have in my database quite a bunch of a models where I do have quite
> large fields and I'm using .only('pk', 'identifier') to fetch only those
> two fields - mainly to make serverside natural sort for a data. Database
> is legacy one and it's b
Hi,
I have in my database quite a bunch of a models where I do have quite
large fields and I'm using .only('pk', 'identifier') to fetch only those
two fields - mainly to make serverside natural sort for a data. Database
is legacy one and it's being used with other external programs as well
so
5 matches
Mail list logo