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.

On Tue, Feb 24, 2009 at 2:59 PM, Avery Pennarun <[email protected]> wrote:

>
> On Tue, Feb 24, 2009 at 5:30 PM, Justin Collum <[email protected]> wrote:
> > Might be related, might not, but dbmetal did interpret the 'Boolean' type
> in
> > the database as a boolean in .net. The create script from SQLite admin
> looks
> > like this:
> >
> > CREATE TABLE [Users] (
> > [Id] INTEGER  PRIMARY KEY AUTOINCREMENT NOT NULL,
> > [UserName] varchar(20)  UNIQUE NOT NULL,
> > [Password] varchAR(20)  NULL,
> > [FirstName] vaRCHAR(20)  NULL,
> > [LastName] varchar(20)  NULL,
> > [Active] BOOLEAN DEFAULT 'Y' NOT NULL
> > )
> >
> > It seems likely that SQLite Administrator is doing something weird with
> > booleans. It's making some assumptions, probably generating a varchar(1)
> > instead. I'm not sure what to do with it.
>
> The important thing about sqlite is it doesn't really have "data
> types" exactly.  You can name your data types anything you want.  You
> could call it a "bigfoolean" if you wanted, and it would still work.
>
> Because of that, there's no completely standard convention on what
> goes into a boolean type.  With that in mind, I'm not really sure how
> you'd do it comfortably in Dblinq.  Maybe an attribute on the
> table/column object that declares what the true/false values of the
> field are.
>
> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to