Verify support for computed columns

[abhishekkumams]

Why make this change?

• Closes #
  • To Verify that DAB engine supports CRUD operations on tables with calculated columns.

What is this change?

• Updating SQL files (MSSQL/MYSQL/POSTGRES) to add a new table containing calculated columns.
• Added Tests to verify CRUD operations on them.

How was this tested?

• Integration Tests

Sample Request(s)

NOTE:

Update Mutation for tables with computed columns currently fail for MySQL( created an issue #1001 to handle the same)

[severussundar]

In the Input Types generated for the create, update and delete mutations, does the computed column show up as an optional field?

IMO, computed columns shouldn't come up because we wouldn't want any kind of input directly provided to the computed columns.

[severussundar]

LGTM after answering few questions!

[abhishekkumams]

In the Input Types generated for the create, update and delete mutations, does the computed column show up as an optional field?

IMO, computed columns shouldn't come up because we wouldn't want any kind of input directly provided to the computed columns.

the computed columns show up as optional column, and if we would try to update it, it will give an error stating that it's a computed column and cannot be modified.