Archive for category ASP.NET CSharp

The specified cast from a materialized ‘System.Int64′ type to the ‘System.Int32′ type is not valid

I ran into a sql related .net error today.  If you read the title of the post you’ve probably guessed what it is.  If not here’s the error:

The specified cast from a materialized ‘System.Int64′ type to the ‘System.Int32′ type is not valid.

Google was marginally helpful, but if you’re like me when you google an error you’re hoping for that post that says:  If you see ABC, then you have done XYZ, do 123 to fix the error.  In this case the error is saying there’s a datatype problem.  Something about a Long and an Int.  My app only has ints.  No longs in the schema at all.  This specific error came out of an entity framework method, so I couldn’t easily pinpoint it to a given column.  98% of my app is pure entity framework, mostly code-first (though I do write out transactional schema patches to update the database in a scripted manner.)  There is one stored procedure in the app, and this stored proc I had just changed to add some new features specifically paging from the sproc.

In this case, the sproc looked like this:

Reports_MyReport SomeGuidID

it returned data of the report, field1,field2, field3 etc..

My change was to add paging directly to the sproc, reduce the amount of data leaving the box as this report was going to get hit a lot.

Reports_MyReport SomeGuid, PageNumber, PageSize

it returns data like RowNumber, Field1, Field2, Field3, TotalRows

I tested out the changes, they worked great, no nulls where they weren’t expected.

Upon running the new sproc through my app, i got the error listed above.  It turned out that my sproc, which had code like this:

select RowNumber, Field1, Field2, Field3, @totalRows as TotalRows  ….

was the culprit.  @totalRows was being interpeted as a int64, as that was comming from an @@ROWCOUNT function.  I know i’ll never have more than int32 rows in that table, so for me switching by casting to Int32 solved the problem:

select RowNumber, Field1, Field2, Field3, cast(@totalRows as int) as TotalRows  ….

Problem solved, error gone!

Hopefully by the time I have completely forgotten about this, and make the exact same mistake again – in six months – this post will be living in the googles.  Hopefully this helps someone else as well.

 

Scott

 

, , ,

Leave a comment

Cleaning Up with MSpec

I use MSpec for testing my code.  I love the behavior driven approach, for me it just makes sense.  I love how if my boss asks where are we with component XYZ, I can just run all my tests and give him the output.  It shows what’s working and what’s not.  Further more, we can say or make a rule that software doesn’t have a feature until there’s an mspec test saying that it does.

I was recently working with mspec doing integration tests – these I usually do to make sure my DAL and my database are structurally compatible – and I kept getting database constraint errors when I reran tests.  It didn’t make a lot of sense as I had a cleanup section in my code and I wasn’t seeing any errors.

It turns out, that if an exception is thrown in the cleanup section you’ll never hear about it.  At least for me, it doesn’t bubble up.  Once I put a breakpoint on the first line of the cleanup I figured it out.  Previously I was thinking it wasn’t even hitting my cleanup code.  It was hitting the cleanup section however, only there was an error in that section.  Hopefully this gets into the googles and helps someone.

using Machine.Specifications;
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;

namespace My.Project.Integration.Tests
{
    public class when_creating_a_mything_record
    {
        protected static IMyThingService MyThingService { get; set; }

		protected static MyThing MyThing { get; set; }
		protected static MyThing SavedMyThing { get; set; }

		Establish context = () =>
        {
            MyThing = new MyThing() {
				Name = "thing",
				Description = "thing one"
			};
			MyThingService = ServiceLocator.Instance.Locate<IMyThingService>();
        };

        Because of = () => Exception = Catch.Exception(() =>
        {
            SavedMyThing = MyThingService.Insert(MyThing);
        });

        It should_not_have_thrown_an_exception = () => Exception.ShouldBeNull();
        It should_have_an_id_that_does_not_match_guid_empty = () => SavedMyThing.ID.ShouldNotEqual(Guid.Empty);

        Cleanup after = () =>
        {
           // If this does not appear to get called. put a breakpoint here.  You may have an exception.
           MyThingService.Delete(SavedMyThing);
        };
    }
}

Leave a comment

Last Day at Telligent

Today was my last day at Telligent.

My first day was February 4th 2005.  By my math – or by datediff() in SQL – that’s 2,646 days.  I started there as a contract employee wondering how long it would last.  I remember leaving a job that I had been in for about three years when I accepted the position at Telligent.  I remember how scared I was of telecommuting.  No office, no managers to watch over me.  What’s to stop total anarchy and no work?  Well absolutely amazing people, incredible clients and the most challenging work of my career.  That’s what.  When asked by friends how I could work from home for a company so far away, and not just play games all day – they didn’t understand the work was the fun and still is up till this very day.  I worked on amazing projects right up until my final hours at Telligent.  I’ll always be more grateful to Rob Howard and Jason Alexander for giving me the opportunity in those early days.  What started as a small group of .net geeks who sometimes did meetings over xbox live & madden football morphed into something amazing.  An incredible company that I still absolutely love and know will continue to do amazing things.   I’m waiting for the day that I hear Telligent’s name in accolades on CNBC , it will come and I will cheer on that day.   To everyone at Telligent, Thank You so much for the amazing seven years.   I think I got to do almost everything a software developer could do at Telligent.  It wasn’t always easy, was sometimes very hard, but I’d not trade any of it for the world.

I look back at the time with incredible fondness and take away many memories.  I look forward to the very near future when I start my new job at Orcsweb.  I’m leaving one amazing place to go to another amazing place.  I could not be happier and couldn’t think of a better place to move on to.   Expect to hear quite a bit more from me about some of the very cool things I’ll be doing at Orcsweb.  I know I’ve been somewhat silent in the past as I worked on other non technical things, writing etc..  But there definitely will be more posts about amazing technologies and what I’m discovering along the way.

Thank You Everyone.

Scott

5 Comments

Massive Data Access Library

Today I got introduced to Massive.  Massive is a data access library written by @robconery.  My co workers @jaymed and @mgroves introduced me to it, and I’ll admit I was somewhat reluctant to give it a shot.  I’m normally of the opinion that the simplest DAL is just pure simple SqlCommands, SqlConnections and a stored procedure call.  However after using Massive for a few hours, I’m really excited about this new tool in my tool chest.  Of course massive has been out for a while, I’m quite slow to the party sometimes.

Massive is great though, I love how in a single line of code I can have data back.  Alternatively I can update the table, or run any other query that I want.  This library if it did nothing else makes integration testing a breeze.  Usually for my tests I prefer to stub out a DAL repository via the interface/repository pattern.  The tests get a FakeSomethingRepository to use that uses List<TheObject> as its in memory store.  What I love about massive is that my unit tests which are really simple because they can test DataRepository.SomeList  can quickly become Integration tests with almost no additional complexity.  For me that’s Huge.  I’m trying a new thing, and that’s not to check in any code that doesn’t have full unit test coverage and Massive is making that happen in a Massive way.  (couldn’t resist)

I’m still learning about these Dynamic things, but a bit of learning never hurt anyone and I know @mgroves will help me out when I get confused.

@robconery If we ever meet, I owe you a beer! Massive is awesome!

If you’re not familiar with Massive, I urge you to check it out here.

1 Comment

Follow

Get every new post delivered to your Inbox.

Join 91 other followers