On Wed, May 14, 2014 at 6:48 AM, Peeyush Agarwal <
peeyushagarwal1...@gmail.com> wrote:
> Hi,
>
> Thanks for the reply :)
>
> Yes, Storing timestamp as timestamp [ (p) ] would be better. I simplified
> the session in question. It may contain alphabets as well. So, I will
> probably need to store i
Hi,
Thanks for the reply :)
Yes, Storing timestamp as timestamp [ (p) ] would be better. I simplified
the session in question. It may contain alphabets as well. So, I will
probably need to store it as a string only.
The problem with types of events is that it is not fixed and will keep
increasin
Why not store session as integer?
And timestamp as timesamp(z?) ?
If you know the types of events, also store them as integer , and save a
map of them in the app or on another table ?
And save the parameters as a json column, so you have more data-types?
Hstore only has strings.
Be carefull wit
