I second this. We would greatly appreciate a fix as we are seeing issues
with DAAP support Banshee in some cases where two systems support IPv6,
including the mDNS layer. Sebastian helped me fix the IPv6 issue in
Mono.Zeroconf for Avahi and Bonjour, and now the problem is in these two
places in
Thanks Ben!
--Aaron
On Wed, 2006-10-25 at 16:51 -0400, Ben Maurer wrote:
Hey guys,
On the 2.0 profile, Encoding uses the char*/byte* version of encoding
methods to avoid allocating memory. One code path missed this
optimization, I've attached a fix.
This code path ends up being used in
are now returned as ints,
rather than longs, for Sqlite3. Similarly for
DATE and DATETIME columns, now returning DateTimes.
I'll do some more probing of this issue.
Cheers,
Aaron Bockover
On Sun, 2006-01-22 at 22:49 +0100, Fredrik Nilsson wrote:
Sorry, forgot to attach
, the value should
always be returned as an Int64, otherwise we risk backwards
incompatibility, and do not conform to the sqlite3 spec, which clearly
states a number in an INTEGER column can occupy up to 8 bytes.
Cheers,
Aaron
On Sun, 2006-01-22 at 18:03 -0500, Aaron Bockover wrote:
Wow. I'm not sure
First of all, this says a lot (I just mentioned it in another reply):
http://sqlite.org/datatype3.html
On Sun, 2006-01-22 at 18:22 -0500, Joshua Tauberer wrote:
Aaron Bockover wrote:
Wow. I'm not sure why this change was made, but in
Mono.Data.SqliteClient/SqliteDataReader.cs, this happens
methods.
Just a thought.
--Aaron
On Sun, 2006-01-22 at 18:41 -0500, Aaron Bockover wrote:
First of all, this says a lot (I just mentioned it in another reply):
http://sqlite.org/datatype3.html
On Sun, 2006-01-22 at 18:22 -0500, Joshua Tauberer wrote:
Aaron Bockover wrote:
Wow. I'm not sure
also not 100% sure I like the ability of INTEGER columns to be
either Int64 or Int32. Maybe they should just always be Int64. Maybe it
doesn't much matter :)
I have also attached a test case showing how slow DateTime.Parse is.
Cheers,
Aaron
On Sun, 2006-01-22 at 18:41 -0500, Aaron Bockover wrote
On Sun, 2006-01-22 at 20:06 -0500, Joshua Tauberer wrote:
Why do you say that dates are in -MM-dd HH:mm:ss format? It
depends on how they were put into the database -- probably the local
encoding if they're put in with DateTime.ToString(), right?
That's how they are stored as strings
