On 22-6-2012 12:58, Bram de Jong wrote:
> On Fri, Jun 22, 2012 at 12:27 PM, Melvyn Sopacua
> wrote:
>> On 22-6-2012 12:09, Bram de Jong wrote:
>>
>>> However, when I turn this field into a filter in the admin, instead of
>>> seeing the filter-versions as my string (i.e. "1.0.5rc3") I see it as
>>
On Fri, Jun 22, 2012 at 12:27 PM, Melvyn Sopacua wrote:
> On 22-6-2012 12:09, Bram de Jong wrote:
>
>> However, when I turn this field into a filter in the admin, instead of
>> seeing the filter-versions as my string (i.e. "1.0.5rc3") I see it as
>> the underlying database type (i.e.1301)
>
>
On 22-6-2012 12:09, Bram de Jong wrote:
> However, when I turn this field into a filter in the admin, instead of
> seeing the filter-versions as my string (i.e. "1.0.5rc3") I see it as
> the underlying database type (i.e.1301)
I suspected there is another code path that doesn't call to_python
Hello all,
I have a custom DB field: a version string like "1.0.5rc3" which is
actually stored as an int in the db.
After fidling around a bit I managed to make the field so that
everything you would think should work works. It looks like a version
string everywhere, I can input it as a version s
4 matches
Mail list logo
