Bug #33176

timestamp trouble

Added by Steffen Gebert about 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Should have
Assignee:
-
Category:
Logging API
Start date:
2012-01-13
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:

Description

  • The field timestamp is called time_micro in the database. Guess renaming to timestamp is fine
  • microtime function "is only available on operating systems that support the gettimeofday() system call". I hope that's kind of every system?
#1

Updated by Ingo Renner about 10 years ago

AFAIR we named it that way because timestamp is a reserved word...

#2

Updated by Steffen Gebert about 10 years ago

Ah, wondered about that, too. Why the hell does TYPO3 not escape field names with backticks?

#3

Updated by Ingo Renner about 10 years ago

I didn't try actually, but stopped considering using timestamp as field name right when it was highlighted in the IDE...

#4

Updated by Philipp Bergsmann about 10 years ago

It's called tstamp in "pages" and "tt_content"...probably stick with that "convention"?

#5

Updated by Steffen Gebert about 10 years ago

But this time it's a different timestamp, as it's a DECIMAL column containing decimal places. So maybe time_micro would really fit best..

#6

Updated by Ingo Renner about 10 years ago

Philipp Bergsmann wrote:

It's called tstamp in "pages" and "tt_content"...probably stick with that "convention"?

The tstamp column there is about the last time the record was changed (so it really should be called "changed" or something like that). Here it is about when the entry was created, which in other tables would be create and which also is bad naming, but that's how we all coded back then ;). And also, here we store more fine grained information - down to micro seconds - compared to just seconds in other places.

#7

Updated by Steffen Müller over 9 years ago

  • Status changed from New to On Hold

I think we should use time_micro which clearly states it's (float) difference to common typo3 (decimal) timestamp fields.

#8

Updated by Steffen Müller over 9 years ago

  • Status changed from On Hold to Resolved

Also available in: Atom PDF