Quote:
Originally Posted by grail
ADDENDUM: Seems I might have jumped the gun. My solution was working but I found that the lastAccessed and creationTime, which I would assume by the names should be dates, both give me very odd date information although the time looks ok, examples:
Code:
lastAccessed has value 1362416667119159 and is a date which is -1413-03-01 13:07:12
creationTime has value 1362416667107908 and is a date which is -1413-03-01 13:07:12
|
These are just Time-Stamp fields, i.e. counting seconds from one of the epochs. In the case of the cookies-file, they are stored as INTEGERs and it would probably be best to not convert them. Only, the SHP gem cannot work with such large integer-numbers. I may thus choose to convert them to floating point by default. If the user names these fields with the --time parameter, they become formatted as seconds from the Unix-epoch. This is all very unsatisfactory, of course.
Even if it looks like a full blown database format, SQLite is first of all... light. And the SHP gem had been developed with completely different uses in mind. I cannot ask for more, at this time.
