R – Question getting started with SubSonic 3 + ActiveRecord

activerecordsubsonicsubsonic3

I am struggling pulling a simple list of records from one table object and printing them out.

I have a table called [Acceptance] that has four fields, two of which allow nulls. Here is the ddl for the schema object:

CREATE TABLE [dbo].[Acceptance](
    [AcceptanceID] [int] IDENTITY(1,1) NOT NULL,
    [AcceptanceCode] [nvarchar](2) NOT NULL,
    [AcceptanceDesc] [varchar](25) NOT NULL,
    [SortOrder] [tinyint] NOT NULL,
 CONSTRAINT [PK_Acceptance] PRIMARY KEY CLUSTERED 
(
    [AcceptanceID] ASC
)WITH (PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON) ON [PRIMARY]
) ON [PRIMARY]

When I try to render a single field of a single record to the console using the following code:

var a = Acceptance.All();
            Console.WriteLine(a.First().AcceptanceID);
            Console.Read();

I get the following exception:

System.ArgumentException was unhandled Message="Object of type 'System.Byte' cannot be converted to type 'System.Boolean'."

None of my fields are of type Bit/Boolean. I'm just not getting it…

Nullable types and Linq Query syntax are 2 topics that I am struggling with…

Any insight into how do this properly is greatly appreciated.

Thanks,

Josh

Best Answer

What DB are you using? I'm going to guess MySQL... you can go into the T4s and change the way the system type is defined. For the default template that's SQLServer.tt, with MySQL its MySQL.tt. Just look for where we set tinyint - it's an ongoing issue (with me at least) with returning byte[] vs bool - set as needed.

Related Solutions

R – Defining SubSonic 3 ActiveRecord migrations

You can still use SubSonic 3 as a DAL and let SubSonic 2.2 generate the migrations for you. You just need sonic.exe and it's dependencies to execute the migration files.

To be more precise, I have folder Migrations in my DataLayer Project, that keeps all the migration Files but set the BuildAction to none. So I have Syntax Highlighting (but no error checking unless I set BuildAction back to compile) but the code does not mess my project.

You can keep them in an own project, of course. But I like it this way to have it under version control and be sure that my current DAL is matching my migration version.

In addition, I have named my config file migration.config (instead of app.config/web.config) and use this commandline to execute my migrations.

Command:           /path/to/sonic.exe  
Arguments:         migrate /config migration.config
Working Directory: $(SolutionDir)MyProject.Datalayer

Notice the /config switch to override the config file sonic.exe is looking for.

R – SubSonic 3 ActiveRecord generated code with warnings

Currently, the only way to get rid of the warnings is to update your t4 templates and submit a bug/fix to Rob. Or wait until somebody else does.

As for the GetHashCode implementation, I don't think you're going to find a good way to do this through templates. Hash code generation is very dependent on what state your object contains. And people with lots of letters after their name work long and hard to come up with hash code algorithms that are fast and return results with low chances of collision. Doing this from within a template that may generate a class with millions of different permutations of the state it may hold is a tall order to fill.

Probably the best thing Rob could have done would be to provide a default implementation that calls out to a partial method, checks the result and returns it if found. Here's an example:

public partial class Foo
{
    public override int GetHashCode()
    {
        int? result = null;
        TryGetHashCode(ref result);
        if (result.HasValue)
            return result.Value;
        return new Random().Next();
    }

    partial void TryGetHashCode(ref int? result);
}

public partial class Foo
{
    partial void TryGetHashCode(ref int? result)
    {
        result = 5;
    }
}

If you compile this without the implementation of TryGetHashCode, the compiler completely omits the call to TryGetHashCode and you go from the declaration of result to the check to see if it has value, which it never will, so the default implementation of the hash code is returned.

Related Topic