Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=78597 --- shadow/78597 2006-06-24 21:16:49.000000000 -0400 +++ shadow/78597.tmp.19033 2006-06-25 15:52:42.000000000 -0400 @@ -246,6 +246,23 @@ Right now the BufferedStream makes it harder to debug under VS.NET as I somewhat loose track of the data. Any light you can shed on the "bad/extra" data would be very useful. Thanks. ------- Additional Comments From [EMAIL PROTECTED] 2006-06-24 21:16 ------- Sebastien, could you make a patch available? + +------- Additional Comments From [EMAIL PROTECTED] 2006-06-25 15:52 ------- + +Ok. I'm almost finishing my reinstallation. I'm using Gentoo and I'm +recompiling my system :) + +If it helps, you can change the BufferedStream creation and use an +Stream instead, in NpgsqlStartupState.cs, line 58. This is the central +place where streams are created inside Npgsql and will not break +Npgsql usage. After a grep, I found that NpgsqlConnectedState is also +using BufferedStream when it doesn't need anymore. I will fix that +later too. + +I'm investigation those invalid values. If I nave any clue about them, +I will post here. + + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
