Instructions to start the Django server
- You should now be running the virtual environment from the project's root folder.
- Run the command "python3 manage.py migrate --run-syncdb" (if this did not work you can also try, "python3 manage.py migrate --run-syncdb")
- You should see something like,
Operations to perform:
Synchronize unmigrated apps: corsheaders, messages, staticfiles, tables
Apply all migrations: admin, auth, contenttypes, sessions
Synchronizing apps without migrations:
Creating tables...
Creating table tables_student
Running deferred SQL...
Running migrations:
Applying contenttypes.0001_initial... OK
Applying auth.0001_initial... OK
Applying admin.0001_initial... OK
Applying admin.0002_logentry_remove_auto_add... OK
Applying admin.0003_logentry_add_action_flag_choices... OK
Applying contenttypes.0002_remove_content_type_name... 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 auth.0009_alter_user_last_name_max_length... OK
Applying auth.0010_alter_group_name_max_length... OK
Applying auth.0011_update_proxy_permissions... OK
Applying auth.0012_alter_user_first_name_max_length... OK
Applying sessions.0001_initial... OK
- Run the command "python manage.py runserver" in order to run the Django server.
Now, the server should be up and running and should be accessible from "http://127.0.0.1:8000/" You should see something like this screenshot with a "The Student List" displayed. You should be able to perform CRUD operations on the student table sufficiently easily.
The currently accessible links are:
-
"http://127.0.0.1:8000/action/listAction" gets the data from the backend to display in the jTable.
-
"http://127.0.0.1:8000/action/createAction" sends data from the jTable to the backend to create a new record.
-
"http://127.0.0.1:8000/action/deleteAction" sends the id of the record to delete from the backend.
-
"http://127.0.0.1:8000/action/updateAction" send the data from the jTable to the backend to update an existing record.
-
To setup admin access to the site, use the command "python3 manage.py createsuperuser" and setup username and password. Launch the server and navigate to the admin page at URL "http://127.0.0.1:8000/admin/" login with the credential and update the database tables / add / delete entries etc.
-
LICENSE
- the Django JTable project is licensed under the MIT License as well like the JTable widget.
- the original JTable widget is distributed in this package but not part of this project jTable is developed by Halil İbrahim Kalkan and licensed under MIT License. See: https://www.jtable.org/Home/About
-
Works with jTable 2.4.0; please download and install this package; it is not distributed with the pypi package.
Notes
- Created: 8/3/2022
- Last updated: 11/17/2025
Metadata
Release files for django-jtable 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django_jtable-0.1.1.tar.gz | 10.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_jtable-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.1 kB
Release files / django_jtable-0.1.1.tar.gz
| Download URL | django_jtable-0.1.1.tar.gz |
|---|---|
| Size | 10.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7525e2724fe1382736b0967a512468a9abc9e4650cdd0e3b3cb76e68e7bb9452
|
|
BLAKE2b-256 checksum How to use checksums |
6409a962e25798cea8ef23b536df785bb193893b3f577d0ba62cbd0fe526f593
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Release files / django_jtable-0.1.1-py3-none-any.whl
| Download URL | django_jtable-0.1.1-py3-none-any.whl |
|---|---|
| Size | 11.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6d18075f7af47eacfda46f808922a617308807adafea55f43ca0339690ea73b3
|
|
BLAKE2b-256 checksum How to use checksums |
c39eb2d5ab0b82656b2e268cd6158bba5dc2765fd13e40a667235ae3b8f5dc0b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Security for django-jtable 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.