Hi,
I have setup a field as VarChar and PK in AppGini. The Rebuild Fields does not show any problems in the Admin-Area. But: When I try to add a record this error shows up (but the record is added to the table).
Olaf
Bug? 5.75: Does AG assume PK is always integer?
Bug? 5.75: Does AG assume PK is always integer?
Some postings I was involved, you might find useful:
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
Re: Bug? 5.75: Does AG assume PK is always integer?
Hi,
the problem also occurs, when I try to change (update) a record.
Olaf
the problem also occurs, when I try to change (update) a record.
Olaf
Some postings I was involved, you might find useful:
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
Re: Bug? 5.75: Does AG assume PK is always integer?
Hi again,
when I try to delete a record (here with PK = yy ) also the error occurs ... which is strange, as the record should have been deleted already.
This time, the record is not deleted.
Olaf
when I try to delete a record (here with PK = yy ) also the error occurs ... which is strange, as the record should have been deleted already.
Code: Select all
Query:
SELECT * FROM ecomo_Lagerorte WHERE `ecomo_Lagerorte`.`ID_Lagerort_Kurz` = yy
Olaf
Some postings I was involved, you might find useful:
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
Re: serious Bug! 5.75: AG assumes PK is always integer!
Hi,
me again. The problem occurs on other tables as well making it impossible to use a non numeric field as primary key.
Please fix in the next version. .... This is some important bug I think.
Why do I want other fields than numeric as PK? At this time AG makes it quite hard to show additional information in a record. One has to create extra fields in the foreign table and use autofill lookup - which is also not very neat when you need a value from a third table in the select. It needs serious workarounds. So my solution is, make my text fields PK (works in my scenario) and I add a integer field which I populate with the "_before_insert" hook with the max number of that field +1 ... effectively creating my own numeric pk.
Olaf
me again. The problem occurs on other tables as well making it impossible to use a non numeric field as primary key.
Please fix in the next version. .... This is some important bug I think.
Why do I want other fields than numeric as PK? At this time AG makes it quite hard to show additional information in a record. One has to create extra fields in the foreign table and use autofill lookup - which is also not very neat when you need a value from a third table in the select. It needs serious workarounds. So my solution is, make my text fields PK (works in my scenario) and I add a integer field which I populate with the "_before_insert" hook with the max number of that field +1 ... effectively creating my own numeric pk.
Olaf
Some postings I was involved, you might find useful:
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
Re: Bug? 5.75: Does AG assume PK is always integer?
Hi,
once again to this bug.
The bug occurs and makes hooks set in the _after_insert break... this function is not executed anymore.
Olaf
once again to this bug.
The bug occurs and makes hooks set in the _after_insert break... this function is not executed anymore.
Olaf
Some postings I was involved, you might find useful:
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
Re: Bug? 5.75: Does AG assume PK is always integer?
Hmm ... AppGini doesn't assume that PK is always an integer ... You could try checking the Customers table from the online demo at https://bigprof.com/demo, where the primary key field is a VARCHAR and it's working fine. Is it possible to send me the AXP project file where this issue occurs please? You could use the support form at https://bigprof.com/appgini/support-request
AppGini plugins to add more power to your apps:
- DataTalk is an innovative AppGini plugin based on ChatGPT that allows you to interact with your AppGini database using natural language questions, without writing any SQL. Check the demo video
- Mass Update plugin: Update multiple records at once and improve your workflow efficiency.
- Check our other plugins and get a generous discount of up to 30% when buying 2 or more plugins.
Re: Bug? 5.75: Does AG assume PK is always integer?
Hi,
I sent the file.
Olaf
I sent the file.
Olaf
Some postings I was involved, you might find useful:
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view