https://github.com/codesetuptest/django-django-11039

SWE-bench instance: django__django-11039

https://github.com/codesetuptest/django-django-11039

Science Score: 26.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
  • Academic publication links
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (6.6%) to scientific vocabulary
Last synced: 9 months ago · JSON representation

Repository

SWE-bench instance: django__django-11039

Basic Info
  • Host: GitHub
  • Owner: CodeSetupTest
  • License: bsd-3-clause
  • Language: Python
  • Default Branch: main
  • Size: 0 Bytes
Statistics
  • Stars: 0
  • Watchers: 0
  • Forks: 0
  • Open Issues: 0
  • Releases: 0
Created 12 months ago · Last pushed 12 months ago
Metadata Files
Readme Contributing License Authors

README.md

SWE-bench Instance: django__django-11039

Repository: django/django Base Commit: d5276398046ce4a102776a1e67dcac2884d80dfe

Problem Statement

sqlmigrate wraps it's outpout in BEGIN/COMMIT even if the database doesn't support transactional DDL Description

    (last modified by Simon Charette)

The migration executor only adds the outer BEGIN/COMMIT ​if the migration is atomic and ​the schema editor can rollback DDL but the current sqlmigrate logic only takes migration.atomic into consideration. The issue can be addressed by Changing sqlmigrate ​assignment of self.outputtransaction to consider connection.features.canrollbackddl as well. Adding a test in tests/migrations/testcommands.py based on ​an existing test for non-atomic migrations that mocks connection.features.canrollbackddl to False instead of overdidding MIGRATION_MODULES to point to a non-atomic migration. I marked the ticket as easy picking because I included the above guidelines but feel free to uncheck it if you deem it inappropriate.

Repository Contents

This repository contains the actual source code from the original repository at commit d5276398046ce4a102776a1e67dcac2884d80dfe. The code is ready for development and testing.

Docker Environment

A Dockerfile is provided to set up the proper environment for this instance:

bash docker build -t swebench-instance . docker run -it swebench-instance /bin/bash

Owner

  • Name: CodeSetupTest
  • Login: CodeSetupTest
  • Kind: organization

GitHub Events

Total
  • Create event: 2
Last Year
  • Create event: 2

Dependencies

Dockerfile docker
  • sweb.env.py.x86_64.2baaea72acc974f6c02079 latest build
package.json npm
  • eslint ^0.22.1 development
  • grunt ^1.0.1 development
  • grunt-cli ^1.2.0 development
  • grunt-contrib-qunit ^1.2.0 development
setup.py pypi
  • pytz *
  • sqlparse *
tests/admin_scripts/custom_templates/project_template/additional_dir/requirements.txt pypi
tests/requirements/mysql.txt pypi
  • mysqlclient >=1.3.13 test
tests/requirements/oracle.txt pypi
  • cx_oracle >=6.0 test
tests/requirements/postgres.txt pypi
  • psycopg2-binary >=2.5.4 test
tests/requirements/py3.txt pypi
  • Pillow * test
  • PyYAML * test
  • argon2-cffi >=16.1.0 test
  • bcrypt * test
  • docutils * test
  • geoip2 * test
  • jinja2 >=2.9.2 test
  • numpy * test
  • pylibmc * test
  • python-memcached >=1.59 test
  • pytz * test
  • pywatchman * test
  • selenium * test
  • sqlparse * test
  • tblib * test