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
Here's a simple scenario: you have a very basic table and you want to perform basic operations on it (SELECT, INSERT, UPDATE, DELETE), e.g.:
typeAdapter= TableAdapter<"SomeTable">
That means we get this code generated, roughly:
typeAdapter={
Select:SQL<"select * from SomeTable">
Insert:SQL<"insert into SomeTable(...) values (...)">
Update:SQL<"update SomeTable set (...) where ...">
Delete:SQL<"delete SomeTable where ...">}
Should be enough for a dead-simple CRUD requirement.
This could get complicated with default values etc., so it should be sufficient to simply mandate usage of all columns. For a more complicated scenario, Date&Darwen's Tutorial D view update system could be considered (but I think it's not that useful in practice).
What do you think?
The text was updated successfully, but these errors were encountered:
This falls in the category of something I don't plan to work on myself, but would accept PRs for.
(As opposed to other enhancements, which I do plan to work on, but will still probably never get around to).
Here's a simple scenario: you have a very basic table and you want to perform basic operations on it (
SELECT
,INSERT
,UPDATE
,DELETE
), e.g.:That means we get this code generated, roughly:
Should be enough for a dead-simple CRUD requirement.
This could get complicated with default values etc., so it should be sufficient to simply mandate usage of all columns. For a more complicated scenario, Date&Darwen's Tutorial D view update system could be considered (but I think it's not that useful in practice).
What do you think?
The text was updated successfully, but these errors were encountered: