# Table Columns in Database **URL:** \ **Category:** Ignition\ **Created:** [November 19, 2018, 5:15pm UTC](https://forum.inductiveautomation.com/t/table-columns-in-database/20948 "2018-11-19T17:15:49Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Schwartzds](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/schwartzds/32/6777_2.png) [@Schwartzds](https://forum.inductiveautomation.com/u/Schwartzds)\ **Post date:** [November 19, 2018, 5:15pm UTC](https://forum.inductiveautomation.com/t/table-columns-in-database/20948/1 "2018-11-19T17:15:49Z")
When I try to pull a query of information out of the table the date and the datevalue is all blank and tstamp values are in long integers. How does anyone suggest querying information and why are those columns like that? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [November 19, 2018, 6:45pm UTC](https://forum.inductiveautomation.com/t/table-columns-in-database/20948/2 "2018-11-19T18:45:05Z")
Using long integers as t\_stamp helps with DB flavor independence and maybe a modest performance optimization on some. Those are milliseconds since Jan 1, 1970. ---
**Author:** ![Paul.Scott](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul.scott/32/4578_2.png) [@Paul.Scott](https://forum.inductiveautomation.com/u/Paul.Scott)\ **Post date:** [November 19, 2018, 7:12pm UTC](https://forum.inductiveautomation.com/t/table-columns-in-database/20948/3 "2018-11-19T19:12:17Z")
Is it safe to assume you’re using the Tag Historian module to collect the records? If so, then try using a [Tag History Binding](https://docs.inductiveautomation.com/display/DOC79/Tag+History+Binding) on the table instead, as it will automatically convert the time for you.