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
Usually, DB-connected services are created on databases that already exist. So, the DB schema is already known and Apigility can automatically configure the DB columns as fields in the REST service. Apigility can also automatically configure some attributes of the fields, e.g. if the field is required, or create a validator that ensures an integer input, etc.
At the moment, after creating the DB-connected service, I have to edit it and add all these fields myself, which is error prone. I have to look at the DB schema and type the exact column names as field names.
This improvement will bring this RAD feature one step forward.
I could not agree more... Hopefully, I've been working on this need and already made a PR that is to be implemented in version 1.1 in about a month.
Basically, it's called "Database Autodiscovery". You'll get an extra-tab on the REST service creation screen. After choosing your adapter, DB Autodiscovery will introspect your DB schema and generate DB-connected services as well as fields, based on column definitions. It's for now stable and just need a bit of cleaning and unit testing.
Stay tuned ;)
Usually, DB-connected services are created on databases that already exist. So, the DB schema is already known and Apigility can automatically configure the DB columns as fields in the REST service. Apigility can also automatically configure some attributes of the fields, e.g. if the field is required, or create a validator that ensures an integer input, etc.
At the moment, after creating the DB-connected service, I have to edit it and add all these fields myself, which is error prone. I have to look at the DB schema and type the exact column names as field names.
This improvement will bring this RAD feature one step forward.
Originally posted by @kaloyan-raev at zfcampus/zf-apigility#37
The text was updated successfully, but these errors were encountered: