![]() I admit, that I do not have an idea how to solve that for My generated code does not crash (create, update, delete work), but in rebuild fields you can not get rid of the memberID warning that in the database it has no PK. To install the AppginiLTE UI simply hit the following file: appginilteinstall.php, so if your project folder for example is: superapp and is on localhost simply hit localhost/superapp/appginilteinstall. It's just confusing to have that warning with no way to remove it anyways. I agree pbötcher, that I could to that in SQL butĪ) would AG still show all names in the list view of the table, even those that are not available anymore (because they have been used already)? I believe not (though I admit, not trying out again - I think I had a similar problem in another table and that did not work - but correct me, if I am wrong).ī) There is no reason for AG to prevent me setting this type of constraint, at least none that I could think of - as it makes perfectly sense.Ĭ) solving this with a SQL approach is imho working around existing possibilities of table/field definition, inventing the wheel again (and from experience, making things worse in the long run).ĪG forces a PK when you want that table as source for a lookup, so I set the PK in AG, but in the database a view can not have a PK. I guess I am trying to make two (or a different point): Hi you this "problem" is not about the SQL for the containers (container-places) you helped me with. As I am quite new to AppGini, you might also suggest using the hooks variant with only one Container table which holds some more details than it does at this time. If you suggest some other way to realize my situation with AppGini, great. I could do this with hooks by hiding these unwanted fields, but it seems much straighter to me not display them at all (never trust user input. How to upload your AppGini web application to a web server using FTP and cPanel AppGini - Web applications in minutes 3.6K subscribers Subscribe 22K views 8 years ago AppGini Screencasts. Why two tables? I want to have a clean view for one usergroup, but another usergroup should see more details. Of course, I can adjust this later on in the database (changing table structure of ContainerDetails), but it seems to me that either I am doing some AppGini handling wrong, or it's an unjustified error (in my use case). ![]() ![]() but this seems to be impossible from the AppGini settings. ![]() Why should this not be possible? If ue UNIQUE is set in the target table (ContainerDetails) one could only open a single entry for each of the records in Container in the ContainerDetails. Field 'ecomo_ContainerSpezifika.ID_Container' cannot be a foreign key and a unique field at the same time. ![]()
0 Comments
Leave a Reply. |