QtScript is currently deprecated, and in Qt 5.6 it will be removed.

I currently use QDjango for one of the components in Ubuntu Touch (the infographics on the lock screen). See (https://bugs.launchpad.net/ubuntu/+source/libusermetrics/+bug/1457488).

Apparently the replacement for QtScript is QJSEngine (http://doc.qt.io/qt-5/qtjavascript.html).

Thanks!

Adds validators for field validation in QDjango. None of this is enabled by default (a la django), but you now have the option of running cleanFields on your model to check for data validation.

currently includes:

• QDjangoRegExpValidator
• QDjangoUrlValidator
• QDjangoIPv4Validator

the tests are basically the same as django

hi there. I think its very useful to make it possible to use aggregate SQL functions on QDjangoQuerySet. I've added AggregateType enum to QDjangoWhere, probably its not the base place for it, but it requires much less changes.

At first glance it's difficult to see how QDjango can help my project; I think users would greatly appreciate some sort of quickstart guide with a simple example on how the library is supposed to be used.

I think a good example is the readme of https://github.com/sandeepmistry/bleno

util.cpp needs QDjangoDatabase::databaseType but it's not exported so I added QDJANGO_EXPORT to QDjangoDatabase class but then the unresolved symbol changes:

QDjangoScript.obj:-1: error: LNK2001: unresolved external symbol "public: static struct QMetaObject const QDjangoDatabase::staticMetaObject" (?staticMetaObject@QDjangoDatabase@@2UQMetaObject@@B)

while qdjangoscript build instead normally, the linux build is fine, but the export keyword is mandatory on win32

One can list the foreign keys to be loaded thus limiting the DB traverse. In the current version the selectRelated loaded all the foreign keys recursively, which is quite demanding for large DB structures.

Is there any specific reason for returning QLatin1String("") here? https://github.com/jlaine/qdjango/blob/master/src/db/QDjangoMetaModel.cpp#L203

It converts null strings to empty strings and bypasses NOT NULL rules. For my case returning QVariant() instead fixed the behavior.

Adds a non template member QDjangoMetaModel QDjango::metaModel(const QObject *model)

It avoids the use of template to retrieve an already registered model, and as a consequence allows one to develop a non template function that saves any QObject in database:

bool storageManager::saveItem(QObject *o)
{
    QDjangoMetaModel meta = QDjango::metaModel(o);
    if(!meta.isValid())
    {
        qWarning() << "Metamodel is not available in storageManager::saveItem for" << o->metaObject()->className();
        return false;
    }
    for(const auto &i : meta.foreignFields().keys())
    {
        meta.setForeignKey(o, i, o->property(i).value<QObject*>());
    }
    return meta.save(o);
}

This is especially useful when using QDjango without QDjangoModel

When creating/droping tables with QDjango::createTables() QDjango::dropTables() check for FK dependencies. Now the tables are processed alphabeticaly.

Example: If I have table A which has foreign key to table B: SQL query "CREATE TABLE A (id integer B_id integer NOT NULL, CONSTRAINT FK_B_id FOREIGN KEY (B_id) REFERENCES B (id) ON DELETE RESTRICT)" Then it ends with error like SQL error QSqlError("1005", "QMYSQL: Unable to execute query", "Can't create table 'DB.A' (errno: 150)")

There is workaround - to run createTables many times (or until there is no error 150).

It would be nice if the createTables() checked for foreign keys first, from these FK dependencies created list of tables in right order and then created those tables.

Hi, I'm working on a desktop application using a WebKit WebView. I'm using QDjangoUrlResolver to deal with routes from WebView requests. I wrote a custom NetworkAccessManager where I translate default QNetworkRequest (and the request body that comes on an QIODevice pointer) to QDjangoHttpRequest, then I invoke QDjangoUrlResolver::respond to do stuff. At the end, I translate QDjangoHttpResponse to QHttpResponse. Thanks, ofrankmartin

As SQLCipher behave just like an SQLite database and it is possible to create a Qt plugin to use it, I think the only change needed to get support to it is to add it on the list of possible drivers on QDjango::setDatabase(QSqlDatabase). Something like: (...) && database.driverName() != QLatin1String("QSQLCIPHER")) I tested it and the only "issue" is the warning, everything else works like a charm. Here is the SQLCipher Qt Plugin project:

https://github.com/sijk/qt5-sqlcipher

django manual: To create a recursive relationship – an object that has a many-to-one relationship with itself – use models.ForeignKey('self', on_delete=models.CASCADE). How can I implement the function in the qdjango?

I recently needed to use a random ordering of query results. To avoid the call to databaseColumn with a non-existing field I added a special case for using RANDOM as a field name and adding the RANDOM() call to the query.

When I add a join to the delete operation (like a "table1___column") for postgreSql, an wrong result query is generated. Like this

DELETE FROM "Table0"
 INNER JOIN "Table1" ON "Table0"."fk" = "Table1"."pk"
 WHERE "Table1"."column" = "something"

Correct query fo this operation like this

DELETE FROM "Table0"
      USING "Table1"
 WHERE "Table0"."fk" = "Table1"."pk" AND "Table1"."column" = "something"

Can there be a notation in the QDjangoModel documentation that explains how to use foreign keys when the models are in namespaces?

It took me quite a while to figure out why

Q_PROPERTY(Model *model READ model WRITE setModel)

fails (at QDjango::createTables()), and should instead be

Q_PROPERTY(modelns::Model *model READ model WRITE setModel)

Hello Jeremy, we are using QDjango in our project for some time now and it worked well. But now we added another database which stores a different type of data. The problem now is that, as far as I can see, there is only a globally registered database connection. We now have to change this connection in each method that does something with the database. Is there a possibility to bind a connection to certain classes? For example registering a property for the connection in the class that inherits the QDjangoModel class.

Best Regards, Daniel