My vote (which you can take or leave) would be to only generate dbml from dbmetal for datatypes that are strictly supported by sqlite. So if it found a boolean when building the classes it should've skipped that table and said "hey, I don't know what to do with a boolean, you'll have to build that yourself".
On Tue, Feb 24, 2009 at 4:43 PM, Avery Pennarun <[email protected]> wrote: > > On Tue, Feb 24, 2009 at 7:41 PM, Justin Collum <[email protected]> wrote: > > That makes sense to me. I solved my problem by switching those columns > over > > to ints. Just have to modify my linq and dbml and i'm done. I think you > > could argue that the issue I'm having is a configuration issue. I'm not > sure > > why SQLite Admin lets you define a boolean type if there is no such thing > in > > the list of SQLite types I referenced. > > Well, people do like their data types :) > > Up until sqlite3, there apparently weren't *any* types. Even ints > were just stored as varchar. That doesn't mean you don't want to > think of it as an integer, though. > > Have fun, > > Avery > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dblinq?hl=en -~----------~----~----~----~------~----~------~--~---
