/opt/jumpserver/apps/perms/migrations/0002_auto_20180723_0150.py - Create model NodePermission - Remove field asset_groups from assetpermission - Addfield date_start to assetpermission - Addfield nodes to assetpermission - Addfield user_groups to assetpermission - Addfield users to assetpermission - Alterfield date_expired on assetpermission - Alter unique_together for nodepermission (1constraint(s)) 2018-07-2301:50:41 [signals_handler DEBUG] Receive django ready signal 2018-07-2301:50:41 [signals_handler DEBUG] - fresh all settings System checkidentifiedsome issues: WARNINGS: ?: (mysql.W002) MySQL Strict Modeisnotsetfordatabaseconnection'default' HINT: MySQL's Strict Mode fixes many data integrity problems in MySQL, such as data truncation upon insertion, by escalating warnings into errors. It is strongly recommended you activate it. See: https://docs.djangoproject.com/en/1.11/ref/databases/#mysql-sql-mode Operations to perform: Apply all migrations: assets, audits, auth, captcha, common, contenttypes, django_celery_beat, ops, perms, sessions, terminal, users Running migrations: Applying assets.0001_initial... OK Applying assets.0002_auto_20180723_0150... OK Applying audits.0001_initial... OK Applying contenttypes.0001_initial... OK Applying contenttypes.0002_remove_content_type_name... OK Applying auth.0001_initial... OK Applying auth.0002_alter_permission_name_max_length... OK Applying auth.0003_alter_user_email_max_length... OK Applying auth.0004_alter_user_username_opts... OK Applying auth.0005_alter_user_last_login_null... OK Applying auth.0006_require_contenttypes_0002... OK Applying auth.0007_alter_validators_add_error_messages... OK Applying auth.0008_alter_user_username_max_length... OK Applying captcha.0001_initial... OK Applying common.0001_initial... OK Applying django_celery_beat.0001_initial... OK Applying django_celery_beat.0002_auto_20161118_0346... OK Applying django_celery_beat.0003_auto_20161209_0049... OK Applying django_celery_beat.0004_auto_20170221_0000... OK Applying django_celery_beat.0005_add_solarschedule_events_choices... OK Applying django_celery_beat.0006_auto_20180210_1226... OK Applying ops.0001_initial... OK Applying ops.0002_celerytask... OK Applying users.0001_initial... OK Applying users.0002_auto_20171225_1157... OK Applying users.0003_auto_20180723_0150... OK Applying perms.0001_initial... OK Applying perms.0002_auto_20180723_0150... OK Applying sessions.0001_initial... OK Applying terminal.0001_initial... OK Applying terminal.0002_auto_20180723_0150... OK 2018-07-23 01:50:45 [signals_handler DEBUG] Receive django ready signal 2018-07-23 01:50:45 [signals_handler DEBUG] - fresh all settings No conflicts detected to merge. (py3) [root@h165 utils]# echo $? 0 (py3) [root@h165 utils]#
本文系转载,前往查看
如有侵权,请联系 cloudcommunity@tencent.com 删除。
本文系转载,前往查看
如有侵权,请联系 cloudcommunity@tencent.com 删除。