The search by content should be faster using native postgresql array type.
Everything else should be the same. We could change it and should be easy.
The problem is backward compatibility. I need to give some thought about
this. Please open a ticket to google code.
On Friday, 1 June 2012 16:49:
Done. Thanks.
Cant we have a custom field for this?
Field.PostgresIntegerList("name")
http://zerp.ly/rochacbruno
Em 02/06/2012 00:26, "Massimo Di Pierro"
escreveu:
> The search by content should be faster using native postgresql array type.
> Everything else should be the same. We could change it and should
Wouldn't that make it non portable to other db's?
mic
2012/6/5 Bruno Rocha :
> Cant we have a custom field for this?
>
> Field.PostgresIntegerList("name")
>
> http://zerp.ly/rochacbruno
>
> Em 02/06/2012 00:26, "Massimo Di Pierro"
> escreveu:
>
>> The search by content should be faster using na
I think list:integer should take advantage of postgres list feature if
available. The issue is how to make it backward compatible to current
implementation.
On Tuesday, 5 June 2012 15:33:37 UTC-5, mcm wrote:
>
> Wouldn't that make it non portable to other db's?
>
> mic
>
>
> 2012/6/5 Bruno
5 matches
Mail list logo