We have some tables of time-series data where the date-time field in the table is not a timestamp or a timestamp_tz typed field, instead it is a numeric value of the unix epoch. Complaints have come because users need to use to_timestamp functions in reporting, and this also causes some caching issues in PowerBI. One solution would be to update the tables with a timestamp-typed column. Another solution being suggested is that a view could be created over those tables that includes (adds) a "normal" timestamp column. My concern is that wouldn't the population of the view constantly redo to_timestamp conversions thus causing much more overhead than a one-time change? Would appreciate input from vertica experts on this.
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.