Comments for Serious Technobabble

Comment on LINQ to SQL pitfalls: Nullable types by Iván Stepaniuk

Iván Stepaniuk — Tue, 29 Jan 2013 23:41:47 +0000

Entity framework suffered from the same problem, but it was fixed in EF4.5 See:http://data.uservoice.com/forums/72025-ado-net-entity-framework-ef-feature-suggestions/suggestions/1015361-incorrect-handling-of-null-variables-in-where-cl?ref=title%23suggestion-1015361

I am currently working with a large codebase that still relies on LINQ to SQL. Since Microsoft has already pulled the plug from it, moving to EF seems the logical next step, sadly that’s not going to happen overnight.

Comment on LINQ to SQL pitfalls: Nullable types by Alexander M. Batishchev

Alexander M. Batishchev — Tue, 29 Jan 2013 23:15:11 +0000

Why do you use LINQ to SQL but not Entity Framework?
Don’t you know does the same issue exist in EF too?

Comment on LINQ to SQL pitfalls: Nullable types by Iván Stepaniuk

Iván Stepaniuk — Mon, 14 Jan 2013 11:26:45 +0000

Thanks Fran (@fran_reyes) for pointing out that option2 causes the same problem. Just clarified that in the post.

Comment on Client-side data compression with JavaScript by Iván Stepaniuk

Iván Stepaniuk — Sat, 12 Jan 2013 21:24:21 +0000

Hey Pierre,
I’m sure the library can handle Chinese characters correctly. Just tried ‘唐’ to be sure, with jSend 2.0.0. PHP class. I also tried with long articles from the Chinese Wikipedia, no problem.

About handling ‘all’ Unicode characters; When translating the PHP class to .NET, I discovered that there are four Unicode 3.2 blocks that can’t pass a round trip (compress in the browser, compare to the uncompressed backend result).

The 4 offending blocks are:
- Private Use Area
- Supplementary Private Use Area-A
- Supplementary Private Use Area-B
- Arabic Presentation Forms-A

It probably fails because of the underlying Unicode implementations differ between the browser and the server. I’m not sure.

You can find a sample of every Unicode block here: http://www.ltg.ed.ac.uk/~richard/unicode-sample-3-2.html

Comment on Client-side data compression with JavaScript by Pierre Clouthier

Pierre Clouthier — Sat, 12 Jan 2013 15:17:35 +0000

Hi Iván -

We are using jsend in our app. There seems to be an error when we try to compress Asian characters (eg: 唐). We get garbage when the PHP decompresses on the server.

Are you aware if jsend can handle all Unicode characters?

Thanks very much for your help.

Pierre

Comment on Client-side data compression with JavaScript by Iván Stepaniuk

Iván Stepaniuk — Mon, 07 Jan 2013 20:16:23 +0000

The jsend.org domain seems to be down for a while. Note that the JavaScript part of this library is now added to my github repo under /jsend.

Comment on List of speakers at the Agile Testing Days 2012 conference, and their Twitter by Carlos Ble

Carlos Ble — Sat, 03 Nov 2012 21:39:51 +0000

Nice list Ivan!
I will come back to it during the event as I meet speakers in person. This way I won’t have to ask for their twitter, just the name :-)

Thanks

Comment on Twitter is currently down for <%= reason %>. by Iván Stepaniuk

Iván Stepaniuk — Mon, 10 Sep 2012 13:22:55 +0000

At the end, it was just a coincidence :)

Comment on Twitter is currently down for <%= reason %>. by Alejandro Piriz

Alejandro Piriz — Thu, 26 Jul 2012 18:06:04 +0000

Maybe some of these share some common datacenter, that could explain the outages

Comment on Castle Dynamic Proxy and moq by Robert

Robert — Thu, 26 Jul 2012 17:30:53 +0000

Glad I came across this post, I was having the same problem and googled for the exact title of this post! Finally did the same thing (using reflection to skip the proxy creation) Thanks for sharing