Duplicate model instance

Is your feature request related to a problem? Please describe. Usually in django to duplicate a model and to not copy every field there is a work around that is pretty straightforward and easy to do. This can be done via setting the pk to None. But with tortoise is not that easy, setting also the attribute ._saved_in_db is necessary.

Describe the solution you’d like Not to access a private variables for this trick to work.

Describe alternatives you’ve considered Maybe a copy method as well, that would be much more intuitive.

Additional context Example of the code needed as of now

book = Book(title='1984', author='George Orwell')

print(book.pk)

await book.save()

print(book.pk)

book.pk = None
book._saved_in_db = False
book.title = 'Animal farm'
await book.save()

print(book.pk)

print(await Book.all().count())

Example of the code that I would like to use instead

book = Book(title='1984', author='George Orwell')

print(book.pk)

await book.save()

print(book.pk)

book.pk = None
book.title = 'Animal farm'
await book.save()

print(book.pk)

print(await Book.all().count())

[grigi]

Released 0.16.13 with clone and implicit change 😄

[grigi]

Normally we only bump the major release if it is a large change that people need to be aware of. And yes, I agree that 0.16 had by now too many releases 🤷

I originally planned 0.17 to include a field refactor so we can support oracle syntax without too many hacks. And so we can differentiate between preparing/escaping data for parameter-passing or inline-SQL or for LIKE. e.g. JSON for Postgresql needs to be a string, but we can’t treat it as a string when it’s inline, because it’s supported natively, it must NOT be quoted like a string.

Also, turns out that Tortoise doesn’t support nullable PK’s for a while now. We generate an error, so my previous case is actually a lot simpler to describe. So the val=None could work for cases where we can generate the pk, and it is now much simpler a condition. pk=None can safely imply _saved_in_db=False.