You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi *,
I am using V. 0.9.5 and built my first PITs with the macro. It seems that the ghost records are not created correctly.
As I am using md5 I would assume a Ghost record with 32 '0's, but the query uses e.g.
CAST('0000000000000000' AS BINARY(16)))
Have you got ghost records enabled in your project?
The 16 0s is coming from the hard coded ghost record in the PIT macro rather than the ghost records feature, which you are correct should be 32 0s so this will be added to the backlog and updated.
Hi Shannon,
ahh thanks. No I did not enable ghost records.
I tested that a few months ago, but this unfortunatelly does not seem to work on our end as we use a lot of weird field names that all would have to be quoted (manually) so I decided to add the ghost record manually.
There is a open bug from me regarding that as well:
As a workaround I changed now all my ghost record entries to CAST('0000000000000000' AS BINARY(16))) - so this works, but to be honest, I am not sure if this could have a bad influence on the performance as CAST('00000000000000000000000000000000' AS BINARY(32))) would be correct...
Thank you
Klaus
DVAlexHiggs
changed the title
PIT table produces wrong ghost values
[BUG] PIT table produces wrong ghost values
May 15, 2024
Hi *,
I am using V. 0.9.5 and built my first PITs with the macro. It seems that the ghost records are not created correctly.
As I am using md5 I would assume a Ghost record with 32 '0's, but the query uses e.g.
CAST('0000000000000000' AS BINARY(16)))
KR Klaus
AB#5359
The text was updated successfully, but these errors were encountered: