-
Notifications
You must be signed in to change notification settings - Fork 16
DbEntity sync #131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
atomashpolskiy
added a commit
to atomashpolskiy/link-etl
that referenced
this issue
Jun 20, 2017
atomashpolskiy
added a commit
to atomashpolskiy/link-etl
that referenced
this issue
Jun 26, 2017
atomashpolskiy
added a commit
to atomashpolskiy/link-etl
that referenced
this issue
Jun 26, 2017
atomashpolskiy
added a commit
to atomashpolskiy/link-etl
that referenced
this issue
Jun 26, 2017
atomashpolskiy
added a commit
to atomashpolskiy/link-etl
that referenced
this issue
Jun 26, 2017
atomashpolskiy
added a commit
to atomashpolskiy/link-etl
that referenced
this issue
Jun 26, 2017
atomashpolskiy
added a commit
to atomashpolskiy/link-etl
that referenced
this issue
Jun 26, 2017
atomashpolskiy
added a commit
to atomashpolskiy/link-etl
that referenced
this issue
Jun 26, 2017
atomashpolskiy
added a commit
to atomashpolskiy/link-etl
that referenced
this issue
Jun 27, 2017
atomashpolskiy
added a commit
to atomashpolskiy/link-etl
that referenced
this issue
Jun 27, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the only possible target type is a persistent Java type, which maps to an ObjEntity in Cayenne. Let's try to extend CreateOrUpdate and Delete scenarios to support syncing DbEntities directly.
The text was updated successfully, but these errors were encountered: