Skip to content
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

[YSQL] DEFERRABLE ERROR #3987

Closed
wolrd opened this issue Mar 17, 2020 · 5 comments
Closed

[YSQL] DEFERRABLE ERROR #3987

wolrd opened this issue Mar 17, 2020 · 5 comments
Assignees
Labels
area/ysql Yugabyte SQL (YSQL) community/request Issues created by external users

Comments

@wolrd
Copy link

wolrd commented Mar 17, 2020

I'm using Django and I got the error:

django.db.utils.NotSupportedError: DEFERRABLE constraint not supported yet
LINE 1: ...type_id") REFERENCES "django_content_type" ("id") DEFERRABLE...
                                                             ^
HINT:  See https://github.com/YugaByte/yugabyte-db/issues/1129. Click '+' on the description to raise its priority

I see the issue #1129 but there is no solution.

When can we expect a solution?

@yugabyte-ci yugabyte-ci added the community/request Issues created by external users label Mar 17, 2020
@ddorian ddorian added the area/ysql Yugabyte SQL (YSQL) label Mar 17, 2020
@ndeodhar
Copy link
Contributor

Hi @wolrd , I'll look into this to get a better understanding of the scope and then give you an estimate of the timeline. We haven't so far prioritized it for 2.2 release (June) but if the scope seems manageable, then we could pick it up sooner.

@wolrd
Copy link
Author

wolrd commented Mar 17, 2020

@ndeodhar thank you for asking.

I didn't understand a little bit. Will the solution be definitely in March or not? Thanks.

@ndeodhar
Copy link
Contributor

No, it won't be in March. I'll check if we can deliver it by June and will give you an update (in 1-2 days) on whether we can have the feature ready by June or after June.

@wolrd
Copy link
Author

wolrd commented Mar 18, 2020

@ndeodhar thanks. I will be waiting for.

The Django community is very large. And I think it will be the right step to allow us to join your product.

And your competitors even have compatibility with Django https://github.com/cockroachdb/django-cockroachdb . We hope you make this decision in favor of Django.

@wolrd wolrd closed this as completed Mar 22, 2020
@rkarthik007
Copy link
Collaborator

Hi @wolrd ,

Just wanted to say that our intention is to totally support Django (and this is irrespective of what our competitors are doing, because Django is a very popular app framework). The issue we're facing is not one of intent, however prioritization. We've been getting requests across the board, and we judge this based on overall community interest.

A couple of things I can suggest:

  • Could you please open a github issue for supporting Django on YugabyteDB? This issue with the DEFERRABLE ERROR may just be one, there could be others. That way, we can keep adding and resolving all blockers to getting there and use that issue as a top level task for the Django ORM support. cc @nchandrappa
  • We're growing as a team as well, so the minute we get more resources and are able to take this task up, we will.
  • We plan to publish our 2.2 roadmap soon (cc @ndeodhar @schoudhury) for the YSQL area especially, please do take a look at that.
  • If you know anyone who would be interested in helping us, we would love to accelerate this effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ysql Yugabyte SQL (YSQL) community/request Issues created by external users
Projects
None yet
Development

No branches or pull requests

5 participants