El 22/12/10 07:00, Phil Thompson escribió:
On Wed, 22 Dec 2010 01:33:49 +0100, Hans-Peter Jansenh...@urpla.net
wrote:
On Tuesday 21 December 2010, 23:58:39 Erik Janssens wrote:
you could just access sql through python instead of through qt,
NULL would then correspond to None
...by the price
On Wednesday 22 December 2010, 07:00:01 Phil Thompson wrote:
On Wed, 22 Dec 2010 01:33:49 +0100, Hans-Peter Jansen
h...@urpla.net
wrote:
On Tuesday 21 December 2010, 23:58:39 Erik Janssens wrote:
you could just access sql through python instead of through qt,
NULL would then correspond
On Wed, 22 Dec 2010 11:56:20 +0100, Hans-Peter Jansen h...@urpla.net
wrote:
On Wednesday 22 December 2010, 07:00:01 Phil Thompson wrote:
On Wed, 22 Dec 2010 01:33:49 +0100, Hans-Peter Jansen
h...@urpla.net
wrote:
On Tuesday 21 December 2010, 23:58:39 Erik Janssens wrote:
you could just
El 22/12/10 12:22, Phil Thompson escribió:
On Wed, 22 Dec 2010 11:56:20 +0100, Hans-Peter Jansenh...@urpla.net
wrote:
On Wednesday 22 December 2010, 07:00:01 Phil Thompson wrote:
On Wed, 22 Dec 2010 01:33:49 +0100, Hans-Peter Jansen
h...@urpla.net
wrote:
On Tuesday 21 December 2010, 23:58:39
Hello,
I currently use the API 1, and use the isNull() method of QVariant to detect
a Null QVariant. This is necessary to detect a NULL value in a database.
It seems there is no equivalent in API2 of PyQt. None is used to model an
invalid QVariant. But how to model a Null QVariant?
Phil Thompson wrote:
The short answer is that you can't. However...
QVariant::isNull() typically delegates to the enclosed data's isNull()
method (eg. QString::isNull()). So your example for API v1 will also work
for API v2.
It gets a bit more complicated if you are also using the
On Tue, 21 Dec 2010 21:06:11 +0100, TP paratribulati...@free.fr wrote:
Phil Thompson wrote:
The short answer is that you can't. However...
QVariant::isNull() typically delegates to the enclosed data's isNull()
method (eg. QString::isNull()). So your example for API v1 will also
work
for
Phil Thompson wrote:
API v1 will be supported until PyQt5 or Python v4.
Is it contractual? Why Python v4? It seems to me that nobody knows when
Python v4 will appear.
Anyway, it seems to be a problem that API2 does not support NULL, even if it
corresponds to side cases (as mine).
Thanks,
you could just access sql through python instead of through qt,
NULL would then correspond to None
On Tue, 2010-12-21 at 23:52 +0100, TP wrote:
Phil Thompson wrote:
API v1 will be supported until PyQt5 or Python v4.
Is it contractual? Why Python v4? It seems to me that nobody knows when
Erik Janssens wrote:
you could just access sql through python instead of through qt,
NULL would then correspond to None
Thanks.
Yes, it is possible to use for example the sqlite3 module, but there are
facilities related to the GUI, available when using Qt: QSqlTableModel,
On Tuesday 21 December 2010, 23:58:39 Erik Janssens wrote:
you could just access sql through python instead of through qt,
NULL would then correspond to None
...by the price of renouncing QtSql neck and crop. That's a high price
to pay, isn't it?
Sure, Camelot does this, but I really
11 matches
Mail list logo
