https://www.gooddata.com/ logo
Join Slack
Powered by
heya, I have a table in the LDM with an attribute ...
# gd-beginners
t
heya, I have a table in the LDM with an attribute 
starts_at
which, when viewing details for the table in the LDM thing, gd recognises as being of type 
timestamp
. All good. However, it doesn't appear as a separate timestamp entity (apologies if I've got the vernacular wrong - but you know, separate blue box), nor when I try to add it am I offered that option (only "text label" attribute" or convert to fact). Any ideas?
m
Hi Thomas, thank you for reach out us, I will look in to the issue and I will get back to you with more details soon.
I am trying to reproduce it, could you confirm the format of the timestamp please?
t
redshift describes it as a 
timestamp without timezone
if I try to add the field to the relevant table in the ldm, it says source type is 
TIMESTAMP
but only offers attribute or fact as options
other tables in our LDM have the same types involved and produce the dates as "separate" entities, I think automatically on adding the table? Not sure
wondering if we've somehow removed that separate entity accidentally and now can't get it back for whatever reason
m
Hi Thomas, thank you for the update and for provide more details. I would like to suggest to check this documentation PrepareYourData-SupportedDataTypes and date-datasets . Also, you must be sure about loading the correct data type that GoodData supports in redshift, namely, 
TIMESTAMP_WITH_TIMEZONE
or 
TIMESTAMP.
You wrote in other tables it is working well, can you check in the tables it is working as expected, which data type is recognized by redshift, 
timestamp without timezone
too?
Hi Tomas, I would like to know if you had time to review the provided documentation. Waiting for your update.
Open in Slack
PreviousNext
Powered by