I wonder if qdjango has html sanitization feature built-in or how one can achieve this?
Thank you!

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?

He guys, how build qdjango to android?

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.

The documentation for QDjangoModel::setForeignKey() says it takes ownership of the QObject* value argument, but what the code does is assign value as a property of the model instance, and this is not taking ownership: a QObject does not delete its properties when it is deleted.

I think the code is doing the right thing, but the doc should be fixed.

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)

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!

With

QList<Variant> numbers = {4, 8, 15, 16, 23, 42};
auto s = QDjangoWhere("number", QDjangoWhere::IsIn, numbers).toString();

s is QDjangoWhere(key="number", operation="IsIn", value="", negate=false)
without the numbers (value is empty).

Note: My real problem is to make something similar to QDjangoWhere::sql or a serialize of a QDjangoWhere and I tried to use the toString() for that.

Hi.

Are you planning on supporting transactions?

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

Hi,

is it possible to create an QDjangoModel object from an arbitrary query that returns the right set of columns?

Regards,
Daniel

I experienced this error when trying to update my local Portfile for qdjango to 0.4.0:

QDjangoMetaModel.cpp:61: error: integer constant is too large for ‘long’ type

full log is here: https://gist.github.com/cooljeanius/7584580

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

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.

I recently started to use QDjango, it's great and works very well !
However, there is one thing which seems not ideal in our context of use : It is nearly impossible to use without template, because of QDjangoQuerySet.
What we aim at is to encapsulate all QDjango access in a single class, which can save, load, delete, all kind of objects in our application. It would be a lot easier if we could just pass/return qobject pointers to these functions without template (for example to connect signals and slots).
I started to modify the QDjangoQuerySet to be template-less, and I have a first version which seems to work. I did not go change the unit tests yet, but I can.
Do you consider it would be worth ? Is there any chance this feature would be merged if i made a pull request ?

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

Hi,

Right now if you modify a field on your model, you need to delete the table to make it work. The select statements use column names that doesn't exist and fails.

I would like to discuss if you are interested on adding a new feature to regenerate the tables (adding columns) if the model changes.

Basically, in createTable(), if the table exists then check the columns of the table and the fields of the model, if any of the fields is not in the table, alter the table accordingly.

Does it have sense? Otherwise, is there any other method instead of removing the table?

Thanks.

Add migration system

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"

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