Craig Fowler comments

Results 32 comments of


                                            Craig Fowler

[Feature Request] Add option to debounce keystrokes in API search

> Just as a point of reference, what is the size of the _site/docfx.json file? Are you sure you meant `_site/docfx.json` and not something else? `_site/manifest.json` perhaps? There is no...

[Feature Request] Add option to debounce keystrokes in API search

That said, for at least one concern listed: > Search index is dynamically created from docfx.json on first page load timing. It consume CPU times. Apparently [this can already be...

[Feature Request] Add option to debounce keystrokes in API search

Hmm, we don't have an `index.json` in the root of `_site` either. The only files which are generated into the root of `_site` which aren't whole HTML pages or obvious...

[Feature Request] Add option to debounce keystrokes in API search

Interesting, on a blank project it is generated but on our main solution's docco project it does not. I compared the `docfx.json` files from our solution and a freshly created...

[Feature Request] Add option to debounce keystrokes in API search

@filzrev I have updated our config, thanks for leading me to discover that it was outdated/malformed. Our docco site has done a full CI and re-published internally. An `index.json` has...

NH generates incorrect SQL (ignoring property-ref mapping attribute) when querying a many-to-one relationship with a subquery that uses EXISTS(...)

> Changing `validOrders.Any(y => y == x.Order)` to `validOrders.Contains(x.Order)` solves your issue. I'll take a further look. Ah, thanks, you are right. Sadly, in our real app, the `.Any(...)` usage...

NH generates incorrect SQL (ignoring property-ref mapping attribute) when querying a many-to-one relationship with a subquery that uses EXISTS(...)

Hi @fredericDelaporte . Thanks for this. I'll add a reminder to - probably - write a third test case which demonstrates the problem as seen on 5.3.16. I don't even...

NH generates incorrect SQL (ignoring property-ref mapping attribute) when querying a many-to-one relationship with a subquery that uses EXISTS(...)

@fredericDelaporte - I've updated the test case (and sample data). It was easier to expand the existing test than write a new one. The comments added to the test indicate...

Incorrect SQL generated for querying property of joined-subclass which is mapped with a formula

As an FYI, I've just seen a colleague repro this sort of bugged behaviour when using Table per class Hierarchy (`` not ``). Once again, NH has naively used just...

Can not use joined-subclass of xml mapping to extend the mappings build with NHibernate.Mapping.ByCode

I've just run into this and I can provide a very good (at least IMO) reason why this scenario should be supported. That's because of issue #1277, for which the...