-
Notifications
You must be signed in to change notification settings - Fork 34
Add Support of Unique contraint #6
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
Would SQL be used for this issue? If so, then can you assign me this issue? |
I would like to work on that. |
Actually I commented: Would SQL be used for this issue? If so, then can you
assign me this issue?
So would SQL be used for in this issue?
Thanks
…On Wed, Mar 4, 2020, 17:41 Ratna Priya ***@***.***> wrote:
I would like to work on that.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#6?email_source=notifications&email_token=AMFZURFDNSGCLL6BSLWKJMDRFZAOTA5CNFSM4GJ5ACXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENXR4MY#issuecomment-594484787>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMFZURDV6ZCWBXF3UU2BHNDRFZAOTANCNFSM4GJ5ACXA>
.
|
@sanchibansal340 yes we have to use SQL properties in the code. |
Hey, I'm participating in GSSOC'21. I wanted to know that for this issue, do we need to make updates in the existing "createtable" method in ambsql.py file or do we need to create a new method. Also, by "writing u after column name" do you mean something like "column_nameU" or " coulmn_name u"? |
create a new method |
while creating table writing "u" after column name should create an attribute with Unique constraint
The text was updated successfully, but these errors were encountered: