On 9 May 2018, at 8:04 am, J Barchan <jnbarchan at gmail.com> wrote:
>> 鈥�
>> On 8 May 2018 at 22:02, Phil Thompson <phil at riverbankcomputing.com> wrote:
>> > On 8 May 2018, at 8:22 pm, J Barchan <jnbarchan at gmail.com> wrote:
> >
> > 鈥�
> >
> > On 8 May 2018 at 18:14, Phil Thompson <phil at riverbankcomputing.com> wrote:
> > On 8 May 2018, at 9:04 am, J Barchan <jnbarchan at gmail.com> wrote:
> > >
> > > 鈥婲ow I'm finding that, with the fix discussed, while my overridden function definition correctly handles database NULLs, it "goes wrong" (as in, different behaviour from before) in certain other cases, returning a QVariant where it did not do so before (it returned the converted, native Python type).鈥�
> > >
> > > 1. So long as I do not override QSqlQueryModel.data() at all, there is absolutely no problem --- both database NULL and auto-conversion of non-NULL to Python native type work fine, and are distinct. This is the situation I need.
> > >
> > > 2. I need to override QSqlQueryModel.data() for my own purposes. If I write just:
> > > def data(self, index: QtCore.QModelIndex, role=QtCore.Qt.DisplayRole) -> typing.Any:
> > > value = super().data(index, role)
> > > return value
> > > Some data conversion happens, such that I no longer get NULL back where the value is NULL --- instead it is converted to '' if string or 0 if int. This was my original problem and is not acceptable.
> > >
> > > 3. Following our discussion, I change that to:
> > > def data(self, index: QtCore.QModelIndex, role=QtCore.Qt.DisplayRole) -> typing.Any:
> > > was_enabled = sip.enableautoconversion(QtCore.QVariant, False)
> > > value = super().data(index, role)
> > > sip.enableautoconversion(QtCore.QVariant, was_enabled)
> > > return value
> > > Now I correctly get whatever for database NULL, which works. However, some other path of code, on some quite different non-NULL value, gets back a QVariant where it used to get a string. I don't know what that path of code is, but I don't think I should care.
> > >
> > > So, what I need is: code which allows me to override 鈥嬧�婹SqlQueryModel.data() but returns the original data() value unchanged, just like it used when I did not put any override in (case #1). It must do whatever to correctly deal with NULL & non-NULL, just like the non-overridden QSqlQueryModel.data() does.
> > >
> > > (In PyQt 5.7) What exact code can I put into the override to achieve just that, please? Surely that can be done, no?
> >
> > You can't have it both ways. Either you let PyQt automatically convert to/from QVariant (and you lose the detection of nulls) or you do it yourself (converting to Python using the value() method).
> >
> > By the way, I've just noticed a bug in the docs which says (incorrectly) that null QVariants are converted to None and vice versa.
> >
> > Phil
> >
> > 鈥婬i Phil,
> >
> > Thanks for your reply.
> >
> > I think one of us must be getting something wrong here. I wonder if you're still expecting me to understand something which is obvious to you but not to me.
> >
> > You can't have it both ways. Either you let PyQt automatically convert to/from QVariant (and you lose the detection of nulls) or you do it yourself (converting to Python using the value() method).
> >
> > I'm not asking to have anything both ways.鈥� I'm just asking how to write code so that the overridden method behaves absolutely identically to the base method it's overriding. Surely that must be possible?
> >
> > I remind you: when I have no override for 鈥婹SqlQueryModel.data() everything behaves perfectly. I am saying: there is no problem, NULLs are handled as such and non-NULLs are correctly converted to their Python equivalent. I do not know how NULLs work (what they are returned as), but everything just works.
> >
> > As soon as I write an override which just returns the base method, it goes wrong on NULL. If I put it the sip.autoconversion(False), it works on NULL but now returns a QVariant where it used to return a Python native type, I think.
>> 鈥嬧�婥orrect - because data() returns a QVariant. With the auto-conversion the Python native type is automatically converted to a QVariant.
>> > All I want to know is: how can I write an override of 鈥婹SqlQueryModel.data() in Python/PyQt like:
> >
> > def data(self, index: QtCore.QModelIndex, role=QtCore.Qt.DisplayRole) -> typing.Any:
> > value = super().data(index, role)
> > return value
> >
> > such that it returns just exactly the same as QSqlQueryModel.data() would have done, please, please, please?
>> 鈥嬧�媃ou already have it - with the calls to autoenableconversion().
>> Phil
>>> 鈥嬧�婥orrect - because data() returns a QVariant. With the auto-conversion the Python native type is automatically converted to a QVariant.鈥�
>> 鈥婩ine. So are you saying I need to replicate the Python auto-conversion on the result I get back because I had to suppress the autoconversion?, and then return that?鈥� Is there a Pyton function, or what sort of code do I need to write, to achieve the same result as whatever the autoconversion would have done? Because I have no idea...
>> 鈥嬧�嬧�媃ou already have it - with the calls to autoenableconversion().
>> 鈥婸hil, no I do not. I very carefully typed in that I had changed over to precisely:
>> > > 3. Following our discussion, I change that to:
>> > > def data(self, index: QtCore.QModelIndex, role=QtCore.Qt.DisplayRole) -> typing.Any:
> > > was_enabled = sip.enableautoconversion(QtCore.QVariant, False)
> > > value = super().data(index, role)
> > > sip.enableautoconversion(QtCore.QVariant, was_enabled)
> > > return value
>> > > Now I correctly get whatever for database NULL, which works. However, some other path of code, on some quite different non-NULL value, gets back a QVariant where it used to get a string. I don't know what that path of code is, but I don't think I should care.
Unless there is a bug in re-enabling auto-conversion, that "other" code path is invoked by the call to the C++ implementation of data(), ie. while auto-conversion is disabled. So you get QVariants, so you can't have it both ways.
> That's exactly what you are saying 鈥�"鈥媃ou already have it - with the calls to autoenableconversion()." about, correct? And I am saying: no, that code returns whatever correct value in the NULL case which I was originally complaining about, but now returns in other cases a QVariant back to my code where it used to return, say, a string. Which then makes the calling code go wrong. So with the calls to autoconversion it does not return the same result as if I had never written the override, which is precisely why I am stumped and asking the question....
You *have* to care about the code paths. To construct a QVariant from a Python value you call the QVariant constructor. To get the Python value from a QVariant you call its value() method.
Phil
More information about the PyQt
mailing list
‘She has never mentioned her father to me. Was he—well, the sort of man whom the County Club would not have blackballed?’ "We walked by the side of our teams or behind the wagons, we slept on the ground at night, we did our own cooking, we washed our knives by sticking them into the ground rapidly a few times, and we washed our plates with sand and wisps of grass. When we stopped, we arranged our wagons in a circle, and thus formed a 'corral,' or yard, where we drove our oxen to yoke them up. And the corral was often very useful as a fort, or camp, for defending ourselves against the Indians. Do you see that little hollow down there?" he asked, pointing to a depression in the ground a short distance to the right of the train. "Well, in that hollow our wagon-train was kept three days and nights by the Indians. Three days and nights they stayed around, and made several attacks. Two of our men were killed and three were wounded by their arrows, and others had narrow escapes. One arrow hit me on the throat, but I was saved by the knot of my neckerchief, and the point only tore the skin a little. Since that time I have always had a fondness for large neckties. I don't know how many of the Indians we killed, as they carried off their dead and wounded, to save them from being scalped. Next to getting the scalps of their enemies, the most important thing with the Indians is to save their own. We had several fights during our journey, but that one was the worst. Once a little party of us were surrounded in a small 'wallow,' and had a tough time to defend ourselves successfully. Luckily for us, the Indians had no fire-arms then, and their bows and arrows were no match for our rifles. Nowadays they are well armed, but there are[Pg 41] not so many of them, and they are not inclined to trouble the railway trains. They used to do a great deal of mischief in the old times, and many a poor fellow has been killed by them." As dusk came on nearly the whole population of Maastricht, with all their temporary guests, formed an endless procession and went to invoke God's mercy by the Virgin Mary's intercession. They went to Our Lady's Church, in which stands the miraculous statue of Sancta Maria Stella Maris. The procession filled all the principal streets and squares of the town. I took my stand at the corner of the Vrijthof, where all marched past me, men, women, and children, all praying aloud, with loud voices beseeching: "Our Lady, Star of the Sea, pray for us ... pray for us ... pray for us ...!" It had not occurred to her for some hours after Mrs. Campbell had told her of Landor's death that she was free now to give herself to Cairness. She had gasped, indeed, when she did remember it, and had put the thought away, angrily and self-reproachfully. But it returned now, and she felt that she might cling to it. She had been grateful, and she had been faithful, too.[Pg 286] She remembered only that Landor had been kind to her, and forgot that for the last two years she had borne with much harsh coldness, and with a sort of contempt which she felt in her unanalyzing mind to have been entirely unmerited. Gradually she raised herself until she sat quite erect by the side of the mound, the old exultation of her half-wild girlhood shining in her face as she planned the future, which only a few minutes before had seemed so hopeless. After he had gloated over Sergeant Ramsey, Shorty got his men into the road ready to start. Si placed himself in front of the squad and deliberately loaded his musket in their sight. Shorty took his place in the rear, and gave out: The groups about each gun thinned out, as the shrieking fragments of shell mowed down man after man, but the rapidity of the fire did not slacken in the least. One of the Lieutenants turned and motioned with his saber to the riders seated on their horses in the line of limbers under the cover of the slope. One rider sprang from each team and ran up to take the place of men who had fallen. "As long as there's men and women in the world, the men 'ull be top and the women bottom." Then, in the house, the little girls were useful. Mrs. Backfield was not so energetic as she used to be. She had never been a robust woman, and though her husband's care had kept her well and strong, her frame was not equal to Reuben's demands; after fourteen years' hard labour, she suffered from rheumatism, which though seldom acute, was inclined to make her stiff and slow. It was here that Caro and Tilly came in, and Reuben began to appreciate his girls. After all, girls were needed in a house—and as for young men and marriage, their father could easily see that such follies did not spoil their usefulness or take them from him. Caro and Tilly helped their grandmother in all sorts of ways—they dusted, they watched pots, they shelled peas and peeled potatoes, they darned house-linen, they could even make a bed between them. HoME一级毛片视频免费公开
ENTER NUMBET 0018zs-tech.net.cn www.yy586.com.cn www.mcpu.com.cn www.b022.com.cn www.egeseramik.com.cn www.nafisa.com.cn www.vitp.com.cn jhyv.com.cn www.lianyili.com.cn www.hcbus.com.cn