-
Notifications
You must be signed in to change notification settings - Fork 378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"repeat" tables creation - parent_id type mismatch #2047
Comments
I think @cheesegrits would say that Fabrik only supports a primary key which is an integer. If you search the forums, some earlier posts say that lists must use internalid element as primary key, but I am reasonably sure that it is not as restrictive as that. Can you not use an internalid element as primary key and keep the Notes document id as a separate element which is indexed and has validations to ensure it is unique? P.S. Since this has not been accepted by the Fabrik team as a bug, can you please transfer this discussion to the forums where it really belongs. |
Thanks for your reply.
But i can't understand why, in table/list creation from CSV import, there's
the option to set which column is the primary key if Fabrik can use only
his autocreated internalid.
That's a little confusing!
I can't usa internalid because relations are built with Lotus notes 32digit
id; mapping this id with the new assigned internalid will generate much
useless work (25.000 rows and 7 repeat everyone)...
I have changed the column type in SQL db and Fabrik works perfectly.
Il Ven 15 Giu 2018, 19:09 Sophist <[email protected]> ha scritto:
… I think @cheesegrits <https://github.com/cheesegrits> would say that
Fabrik only supports a primary key which is an integer.
If you search the forums, some earlier posts say that lists must use
internalid element as primary key, but I am reasonably sure that it is not
as restrictive as that.
Can you not use an internalid element as primary key and keep the Notes
document id as a separate element which is indexed and has validations to
ensure it is unique?
P.S. Since this has not been accepted by the Fabrik team as a bug, can you
please transfer this discussion to the forums where it really belongs.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2047 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ADVTJtr0b9J4SamE-XHOGaIg1EWBGQIHks5t8-pfgaJpZM4Upz77>
.
|
Exactly - I don't think you are restricted to internalid (though that may have been the case in the past), but I am reasonably certain that Fabrik only supports integer primary keys. However, a change to the code to make the repeat group parent_id field match the type of the parent primary key field might not be that difficult for you to code if you wanted to try it. Though you would quite likely be on your own if anything else stopped working when the primary key was a varchar (which I would rate as moderately likely). |
My primary key is not an internalid; I use a unique calculated 32digit string (MYSQL type VARCHAR) as a primary key (without auto-increment), because is a migration from Lotus Notes and documents ID have this format.
When I create a repeatable group, the parent_id column is created as INT, not the original datatype of the value.
The text was updated successfully, but these errors were encountered: