Ed,
> Instead of storing the client_addr as a VARCHAR(255), how about
> storing it instead as a 32bit number in a column of type UNISIGNED
> INT? This'll reduce storage and speed queries.
>
> MySQL can convert back and forth using inet_aton and inet_ntoa.
> Perhaps there's something similar for p
Ed Walker wrote:
Instead of storing the client_addr as a VARCHAR(255), how about storing
it instead as a 32bit number in a column of type UNISIGNED INT?
This'll reduce storage and speed queries.
MySQL can convert back and forth using inet_aton and inet_ntoa.
Perhaps there's something sim
Instead of storing the client_addr as a VARCHAR(255), how about
storing it instead as a 32bit number in a column of type UNISIGNED
INT? This'll reduce storage and speed queries.
MySQL can convert back and forth using inet_aton and inet_ntoa.
Perhaps there's something similar for postgres
