While migration from mysql 5.6 to mysql 8. do we have to change the ROW_FORMAT to dyanmic (depends on innodb_file_format) to prevent any future complications or let it be to COMPACT.
note[in mysql 5.6 we have row_format COMPACT and it is found that innodb_file format removed in mysql 8]
Related
I tried to connect to Sybase database from Django using sqlanydjango, but
I have stuck. One answer saying that
sqlany-django is no longer maintained; it was last updated in May 2016.
What is the other possibility to connect to Sybase database?
OS Ubuntu 18.04
django 2.2.4
Sybase is no longer maintained and it's not supported by Django. I recommend using one of the supported databases:
PostgreSQL
MariaDB
MySQL
Oracle
SQLite
Personally, I would recommend using PostgreSQL - I think it's the most advanced database. If you use it, I would recommend using version 13, since version 14 is still new and I think it's not officially supported by Django yet. It's always a good practice to use the previous major release. Also with Django, I recommend upgrading to the latest major release only about 4 to 6 months after its initial release. So for today, this means using Django 3.2 (latest minor release, currently 3.2.11).
You can use django-environ to define the database you are using in settings.
You could use the freetds module. GitHub repository was active 5 days ago, it aims to provide support for sybase and MSQL Server.
I used it with MSQL
You can download it from there, and installing with the instruction on this link (Sybase python module website)
Then you can test your installation using these steps
You can also try different Django version.
If this doesn't show anything wrong, and Django still won't connect to your DB, you can try to edit Django's source files so the ImproperlyConfigured exception doesn't raise (REALLY REALLY RISKY, DO A BACK UP OF YOUR DB) or migrate your Sybase to a supported database.
You can use pyodbc.
To install this.
Pip install pyodbc
import pyodbc
cnxn = pyodbc.connect(‘DRIVER={Devart ODBC Driver for ASE};Server=myserver;Port=myport;Database=mydatabase;User ID=myuserid;Password=mypassword;String Types=Unicode’)
For reference:-
https://medium.com/#sharma.jayant1992/best-way-to-connect-python-with-sybase-database-76445713efaf
I want to use aurora, but I am using Version 12.5. How can I migrate to aurora?
I think the problem is the version 12.5, so my idea would be to downgrade to 11, but is there not an easier way?
migrate snapshot is grey and cannot be used
Based on the release notes of Django, it seems that:
Support for Mysql 5.5 is dropped in Django 2.1
Support for MariaDB 10.1 and higher is added in Django 3.0
We currently use Django 2.0 with MariaDB 5.5, we'd like to upgrade to Django 3.0 and MariaDB 10.4.
What would be the suggested upgradepath to get to the latest version of Django and MariaDB?
Is Django 2.1 and 2.2 compatible with MariaDB 5.5 and should we upgrade to Django before upgrading MariaDB?
Or is unofficial support for MariaDB 10.x sufficient in Django 2.1 and Django 2.2 and should we just upgrade to MariaDB to 10.4 first?
The "added support" for MariaDB is mostly in name only (https://code.djangoproject.com/ticket/29548 and https://github.com/django/django/commit/b6c4766f53cf00bcf63cc2aa8be977c8589d083e) and is achieved through the mysql database backend. Assuming you are using the recommended mysqlclient version (1.3.13 or later) the safest upgrade strategy would be to first upgrade MariaDB 10.4.
Once that works I would recommend reading (and following) Django's upgrading docs: https://docs.djangoproject.com/en/3.0/howto/upgrade-version/ to get to Django 3.0
With Django >= 3.0, MariaDB is officially supported.
Django now officially supports MariaDB 10.1 and higher.
I was using the vtiger 5.4 and gradually upgraded to 6.5. Now when I tried to upgrade to vtiger 7, its showing the blank page. My version is not matching with the pre-requisites.
What I have the versions are as below:
PHP Version:
C:\vtigercrm-5.4.0\php>php -v
PHP 5.2.6 (cli) (built: May 2 2008 18:02:07)
mysql> select version();
+----------------------+
| version() |
+----------------------+
| 5.0.51b-community-nt |
+----------------------+
Apache Version:
C:\vtigercrm-5.4.0\apache\bin>Apache -v
Server version: Apache/2.0.52
How can I upgrade this to the next level, so that I can continue the Vtiger 7 migration?
If you have no custom code of your own, I would suggest the following steps -
Backup your code and database for 6.5
Uninstall your vtiger 5.4 version
Install XAMPP with PHP7.1 support. Moving away from the standard vtiger installer will let you upgrade to future versions of PHP/apache without this hassle.
Import your database to this new XAMPP and setup the code (you will need to change the config.inc.php)
If everything goes fine, you should have your 6.5 version back working normally and you should be able to upgrade to vtiger 7.
Some pointers -
The new XAMPP installation will have different PHP/mysql settings
Check the Mysql UTF-8 support when creating db
Don't panic if you see lot of notice/warnings, it just means your php.ini is not configured properly yet
Im a beginner to django.
Someone help to connect Oracle 11g db with django 2.0 in windows. What is the requirements and how to connect and what are the changes to be done.
According to the manual,
Django supports Oracle Database Server versions 12.1 and higher. Version 5.2 or higher of the cx_Oracle Python driver is required.
You may run in to trouble with version 11g -- but if you want to give it a shot, that link has the instructions.