Could it be the server doesn't have the database ?


[image: --]

Maninder Kumar
[image: http://]about.me/maninder.s.kumar
<http://about.me/maninder.s.kumar?promo=email_sig>




On Thu, Jan 23, 2020 at 1:49 AM Victor Guimarães Nunes <
[email protected]> wrote:

> Hi,
>
> I'm having some trouble setting up a Django project with a MySQL NDB
> Cluster. I found I had to set the storage engine on
> DATABASES['default']['OPTIONS'] and I did it.
>
> DATABASES = {
> 'default': config('DATABASE_URL', cast=db_url)
> }
>
> # Check if mysql database engine is NDBCLUSTER
> if config('USE_NDBCLUSTER', cast=bool, default=False):
> DATABASES['default'].update({
> 'OPTIONS': {
> 'init_command': 'SET default_storage_engine=NDBCLUSTER;',
> }
> })
>
> but almost always when I try to perform some write action on the database
> I get the following esception:
>
> OperationalError at /admin/auth/user/add/
>
> (1178, "The storage engine for the table doesn't support SAVEPOINT")
>
>
> I don't quite get what I supposed to do about once the cluster demands a
> NDBCLUSTER storage engine to work properly and I don't have any ideia of
> what is savepoints and where/how I can disabled it.
>
> Any thoughts about this issue?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/d3b6be1a-acb1-4543-b8f2-780b8ef5b62d%40googlegroups.com
> <https://groups.google.com/d/msgid/django-users/d3b6be1a-acb1-4543-b8f2-780b8ef5b62d%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CABOHK3TMfgoPNNr%2BAU_6UDdO6SjhAzMeTuvpu1E4BDrUyuCqqw%40mail.gmail.com.

Reply via email to