AppGini insists that a view have a primary id

If you're a new user of AppGini, feel free to ask general usage questions, or look for answers here.
Post Reply
Diogenes
Posts: 16
Joined: 2015-05-07 14:03

AppGini insists that a view have a primary id

Post by Diogenes » 2016-01-14 09:56

I use CRUD tools that do not insist that a View have a primary key

AppGini has brought me to a halt immediately as I try to generate code by not generating any code for the whole project until I kick this view out of the project, regenerate the new project file. Restart AppGini, retrieve the project file, get back to work.

This View is NOT a table and as far as I know a view natively does not contain an index

I need this view to be installed on the database to perform its lookup function on joined tables without asking php to also construct this everytime the query comes up.

I don't see any advice from AppGini on this not uncommon issue

Sometimes primary id's are not that useful and can not be applied to a created view

If Appgini is going to have its own proprietary requirements I am also really slowed down because AppGini only announces its objections when the Code generation is requested, and THEN does not simply show a list of ALL its "problems" in one list

The step-at-a time discovery, fix, discovery, fix...etc approach fix one problem, re-save, then learn of a new problem or one problem at a time is a drag to just wanting to get in and fix errors in one fell swoop.

How do I get around this in the next few hours?

Thank you!

Post Reply