DB Writer Caching Data Type

Hi,

I’m joining data from Google Analytics 4 and Oracle. I’m attempting to pull the data from GA4 into Oracle using DB Writer, but it keeps telling me the data type is too small for one of the columns. The problem is that there is no data type definition and the mapping only maps by data type and has no way to define the string length.

Seems like it should be straight forward based on the node description, but it doesn’t appear to pick up the data type from GA4 and create the table using the same data types. I tried creating the table first using db table creator, but then it won’t map an integer value to from GA4 to an int data type.


image

Maybe I should do the whole thing in python, but thought this would be faster.

I answered part of my own question. DB writer doesn’t provide a way to rename columns so when I created a new table it wouldn’t map those columns coming out of GA to the new table. The only way to make this work was to use the names from GA, which aren’t exactly conventional. So that worked, but it’s a bit wonky because ideally you want to build a table with the appropriate nomenclature and then insert the values from the source. I’m puzzled by the logic. Even a name mapping option along with the data type mapping would be more intuitive.

Hi @kevinnay , can you not put a Column Renamer or a Table Manipulator node between the Google Analytics Query and the DB Writer to rename the columns ?

Also yes the data type mapping isn’t perfect but does this post help at all?

1 Like

Column renamer is a good idea. I’ll give that a shot. Thanks.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.