Wilson ORMapper Forums : Bugs & Issues

Null reference to list in many to many relationship

Thu, 01 May 2008 17:10:58 GMT

How is focus.TitleList being initialized? You probably need to have the mapper create your focus object for you (using ObjectSpace<T>.Create()) so that the TitleList collection gets initialized.

Null reference to list in many to many relationship

Thu, 01 May 2008 14:48:35 GMT

I have a many to many relationship created in my database with FK constraints to the related tables. I am trying to add to the list of objects for each item selected in a check box. See code below. I am getting a null object reference to the focus.TitleList and I don't understand why. I created a new instance to my focus object so that is not null, but why would the TitleList be null?

focus = new UnitVisitTracking.Business.Focus();

foreach (ListItem item in this.TitleList.Items)

{

if (item.Selected)

{

UnitVisitTracking.Business.Title newTitle = UnitVisitTracking.Business.Title.RetrieveByKey(Convert.ToInt32(item.Value));

if (newTitle != null)

{ focus.TitleList.Add(newTitle); }

}

Fetching a mapped object inside a transaction?

Tue, 22 Jan 2008 16:26:06 GMT

I think I recall you mentioning having implemented this capability but hadn't released it yet. Do you plan on making it available?

Thanks!

RetrievePage and WhereClause problem

Fri, 07 Dec 2007 07:38:52 GMT

Problem solved. The WHERE clause was missing parenthesis around the group of fields being OR'd which were then being AND'd with additional fields!

Thanks for the prompt response.

RetrievePage and WhereClause problem

Thu, 06 Dec 2007 22:31:39 GMT

What is "invalid" about the results? Have you tried the same query in Sql Studio or Query Analyzer? What kind of results are you getting there?

RetrievePage and WhereClause problem

Thu, 06 Dec 2007 21:07:33 GMT

I'm using the RetrievePage method to populate a grid using a simple paging mechanism.When I specify a WHERE clause that contains an OR expression, the RetrievePage method returns invalid results. The RetrievePage method works fine when I use a simple WHERE clause with a single field. Can you help?

1. The following WHERE clause works:
field1 LIKE '%foo%'

2. The following WHERE clause gives invalid results:
field1 LIKE '%foo%' OR field2 LIKE '%foo%'

Regards

Martin

IObjectSet.Remove method

Wed, 28 Nov 2007 17:29:52 GMT

Since IObjectSet<T> inherits Collection<T>, there is an inherited Remove(T item) method that can be called, thus bypassing the not supported Remove(object entityObject) method in ObjectSet<T>. Is this desired? Does it work (I haven't gotten that far in unit testing)?

If not, this could be fixed by changing the (object entityObject) arguments to (T entityObject) and using the new keyword. To the best of my knowledge, these arguments should be T anyway.

I'm pretty sure I'm looking at the latest source code (SP).

Thanks, Jamie

IList vs List

Wed, 12 Sep 2007 14:04:52 GMT

As far as I know --- you should use IList<T> (or ObjectSet<T>, which implements IList<T>) if you want lazy-loading. List<T> will not support this.

IList vs List

Mon, 10 Sep 2007 21:56:13 GMT

I just ran into an issue with one of my applications:

When the mapped member in a OneToMany relationship is List<T> it ignores the lazyLoad attribute and loads it anyway. When setting the member type to IList<T> it does in fact lazy load.

Not sure if this is by design or not, but it might help others chase down performance problems.

Delete from many to many with transactions and IObjectNotification

Sun, 09 Sep 2007 08:01:16 GMT

Hi Paul,

Sorry it took me so long to respond.

Regarding the relationships, I was following the many-to-many relationship example I saw somewhere on this site (I think in a forum message), which only implemented the relationship one-way.

In any case, I fixed the problem by fixing the relationships in the database. It seems I forgot to cascade the deletions on both sides of the many-to-many table. Once I did that, everything worked very smoothly.

In fact, I was able to remove the OnDelete IObjectNotification implementation, since the database deletion takes care of the cascade (which is what I was really trying to enforce in the code).

Thanks,
Noam

btw, there's a problem with the html editor in firefox, where it seems to run some javascript loop endlessly. Firefox is able to monitor these infinite loops and abort them, but it's annoying because it takes some time for it to pick up on it.

Delete from many to many with transactions and IObjectNotification

Mon, 27 Aug 2007 18:06:14 GMT

Hi Noam:

The reason you're not getting deleting a product to automatically also delete productstocategories is because you don't have that relationship setup for products -- you only have it setup the other way. As for the IObjectNotification event, you have the ability to do anything you want with the transaction that you are given, including creating and executing your own command. On the other hand, if you simply pass that transaction on to some other "SaveWithTransaction" method, then if there's a questionable order to the sql operations then I would take a look at that "SaveWithTransaction" method.

Thanks, Paul Wilson

Delete from many to many with transactions and IObjectNotification

Mon, 27 Aug 2007 08:30:31 GMT

I tried to post this before, but it doesn't seem to have shown up, so I apologize if this post appears twice.

I have the following many to many relationship in the db:

ProductCategories (ProductCategoryId, fields)
ProductsToCategories (ProductCategoryId, ProductId)
Products (ProductId, fields)

In mappings.config, I have the following mappings:

    <entity type="Logic.Product" table="Products" keyMember="_productId" keyType="Auto">
        <attribute member="_productId" field="ProductId" alias="ProductId" oledbtype="Integer" cstype="int" vbtype="Integer" />
    </entity>
    <entity type="Logic.ProductCategory" table="ProductCategories" keyMember="_productCategoryId" keyType="Auto">
        <attribute member="_productCategoryId" field="ProductCategoryId" alias="ProductCategoryId" oledbtype="Integer" cstype="int" vbtype="Integer" />
        <relation relationship="ManyToMany" member="_products" field="ProductId"
             type="Logic.Product" alias="Products" lazyLoad="true"
             table="ProductsToCategories" sourceField="ProductCategoryId" destField="ProductId"
             />
    </entity>

I've used a slightly modified version of Paul Welter's CodeSmith templates to generate my classes with IObjectNotification. This generates the Products property correctly on the ProductCategory class.

When I delete a product, it does not get automatically deleted from ProductsToCategories. Is there a way to set it up to do this automatically?

In the meantime, I've implemented the IObjectNotification.OnDeleting method in Product.cs as follows:

        public void OnDeleting(Transaction transaction)
        {
            string opath = "Products[ProductId = ?]";
            OPathQuery<ProductCategory> query = new OPathQuery<ProductCategory>(opath);
            Collection<ProductCategory> categories = DataManager.ObjectSpace.GetCollection(query, ProductId);
            foreach(ProductCategory category in categories)
            {
                category.Products.Remove(this);
                category.SaveWithTransaction(transaction);
            }
        }

The problem is that the it seems that this adds this category save operation *after* the product delete operation in the transaction itself. But shouldn't any operations added to the transaction in OnDeleting (or OnUpdating and OnCreating, for that matter) be added first?

It seems like a minor change in order of operations, but I also don't know what other consequences this might have?

Is this a bug, or is it by design?

Thanks in advance,
Noam

SQL Server 2005 Schema problem and paging ...

Sun, 12 Aug 2007 03:58:04 GMT

Did you try the "as temptable" fix I mentioned in that thread? That has worked for me with no issues.

Queries on Abstract Base Classes Not Working

Wed, 08 Aug 2007 01:17:39 GMT

Hi Brad:

I believe my expectation in a case like this was that you wouldn't map CategorizedItem since its not adding anything as far as the mapper is concerned.

Thanks, Paul Wilson

Queries on Abstract Base Classes Not Working

Tue, 07 Aug 2007 06:19:42 GMT

Hi, Paul,

Here's a bit of my class hierarchy:

Item (abstract, entity in mapping file, typeField="ItemType")

CategorizedItem (abstract, inherits Item, subEntity in mapping file, typeValue=1)

LineItem (inherits CategorizedItem, subEntity in mapping file, typeValue=2)
StaffingItem (inherits CategorizedItem, subEntity in mapping file, typeValue=3)

When I try this code:

ObjectSpace os = Manager.Engine.GetObjectSet(typeof(CategorizedItem), "")

the mapper's SQL criteria, as viewed by SQL Profiler, specifies 'ItemType = 1'

This doesn't return any values, even if I have LineItems and StaffingItems in the table, because their ItemType values are 2 and 3, respectively.

Am I missing something? The Mapping File Options wiki entry says that if CategorizedItem is abstract, I don't need to supply a typeValue, but if I don't, the mapper doesn't initialize, saying a typeValue hasn't been specified for CategorizedItem.

Regards,

Brad

SQL Server 2005 Schema problem and paging ...

Tue, 19 Jun 2007 20:10:11 GMT

This appears to be unresolved unless I missed something:

http://ormapper.net/Forums/Default.aspx?part=74&action=thread&id=2412&key=i0S4w%2fsmADcZL3fg5Vk%2bLg%3d%3d

I'm having the same problem using the MS AdventureWorks DB that uses schemas profusely (e.g. Production.Product).

Any fix?

Thanks - wayde

Trick to allow SQL Server 2005 paging without a sort criteria.

Tue, 19 Jun 2007 19:14:56 GMT

I'm still getting the exception whenever I attempt to include paging against a sql 2005 db. Any ideas???

Wilson.ORMapper.ORMapperException: ObjectSpace: Paging requires a Sort Clause

ObjectDataSource declaration:

<asp:ObjectDataSource ID="dsMessages" runat="server" TypeName="WORW.Data.ProductService"

OldValuesParameterFormatString="original_{0}"

SortParameterName="sortClause"

EnablePaging="True"

SelectMethod="RetrievePage" SelectCountMethod="RetrieveTotalRecordCount"

DeleteMethod="Delete" OnDeleting="dsMessages_Deleting"

InsertMethod="Insert" OnInserted="dsMessages_Inserted" OnInserting="dsMessages_Inserting"

UpdateMethod="Save" OnUpdating="dsMessages_Updating">

<asp:Parameter DefaultValue="1" Name="startRowIndex" Type="Int32" />

<asp:Parameter DefaultValue="20" Name="maximumRows" Type="Int32" />

<asp:Parameter DefaultValue="Name" Name="sortClause" Type="String" />

</SelectParameters>

</asp:ObjectDataSource>

Sorting problem when "alias" != "field"

Tue, 19 Jun 2007 19:12:44 GMT

I'm working on a demo that illustrates how WORM can be used in conjunction with the GridView/ObjectDataSource. Anwyays, it appears that sorting doesn't work when the "alias" != "field"

Example:

<attribute member="id" field="ProductID" alias="Id" type="System.Int32" /> (in mapping.xml)

<asp:BoundField DataField="Id" HeaderText="Id" InsertVisible="False" ReadOnly="True" SortExpression="Id" /> (in asp:gridview)

The exception:

System.Data.SqlClient.SqlException: Invalid column name 'Id'.

But I don't get it! The whole idea of the "alias" attribute is to abstract your object property names from the corresponding table column names ... WORM should be smart enough to use the "field" attribute irregardless of whether "alias" is used or not.

Am I missing something here???

Thanks - wayde

Unnecessarily loading lazy-loaded relations when deleting an object

Fri, 08 Jun 2007 21:51:06 GMT

Hi, there - I think I have just run into this, too. When a lazy-load child list is not yet loaded and you try to delete the parent, the child list gets loaded. This is normally not a problem, except when the child entities have lazy-loaded child lists themselves (grandchildren).

Consider this graph of classes A, B and C

A:1 (parent)
--B:1 (child of A:1)
----C:1 (child of B:1)
--B:2 (child of A:1)
----C:2 (child of B:2)

If A1's list of B is loaded, and both of B's lists of C are loaded, worm can successfully delete A:1 by:

Delete all C where parent is B:1
Delete all C where parent is B:2
Delete all B where parent is A:1
Delete A:1

BUT, if A:1's list of B is not yet loaded and worm tries to delete A:1, this happens:

Load all B where parent is A:1
Load all C where parent is B:1
Delete all C where parent is B:1
Load all C where parent is B:2.........CRASH!

Step 4 causes a timeout (in SQL Server anyway) because the C table is locked by the delete in step 3.

This is easy to see by running a trace and watching. Can anyone else confirm this behavior?

Thanks, David Martines

Trick to allow SQL Server 2005 paging without a sort criteria.

Wed, 06 Jun 2007 22:48:32 GMT

Paul, in the last code I sent you, if you try to page over a SQL 2005 we decided to throw if no OrderBy criteria was set and you try to page using the SQL 2005 Provider. Turns out if you want you can order by a bogus criteria in the OVER clause like ORDER BY CURRENT_TIMESTAMP so we don't have to throw. Want that code?

Plurals

Tue, 01 May 2007 23:10:52 GMT

First, lets be clear, that's not the ORMapper doing that -- its code generator you are using, probably either my ORHelper or the CodeSmith templates some have donated. I seem to recall there being an option to turn that off in the CS templates, but even if I'm wrong that's not hard to change in the templates yourself, and the ORHelper gives you the ability to edit things before generating code, although kludgy. Anyhow, even if not you just go with the default in code gen, you can modify it afterwards -- the ORMapper will use what you specify. As for why this is the default -- because its simply standard database practice to name tables with plural form while its standard OO practice to name objects with singular form.

Thanks, Paul Wilson

Plurals

Tue, 01 May 2007 23:06:15 GMT

I've been testing the ORMapper with a set of SQL 2005 tables. Everything seemed to work, but the resulting classes lacked the "s" at the end of my table names. Thus, the Attributes table became the Attribute class. This caused problems in the .NET code, because the Attribute property now has the same name as its containing class. What is the rationale for removing the plural?

The workaround, of course, is to rename all my tables and run the mapper again, but if there is a simpler suggestion I'd appreciate it.

Error during rollback/Zombie message

Tue, 01 May 2007 23:05:36 GMT

This solution worked for us as well. Wow! That was a nasty one. Thanks guys!

-Justin

Updating Table

Tue, 01 May 2007 23:05:25 GMT

Hi There, I'm not sure you if typed the code or done a copy/paste but you are missing a closing parenthesis after "CompanyId == 123" to close the OPathQuery class Constructor.

it probably should be:

OPathQuery query = new OPathQuery(typeof(PerryWorld.Productfolio.BusinessObjects.TblCompany), "CompanyId == 123");

Error during rollback/Zombie message

Tue, 01 May 2007 23:04:44 GMT

I can definitely acknowledge that you and a few others are obviously encountering a very real problem. I hesitate to call it a bug since I know the previous problem like this that I had fixed was due to a bug in ADO.NET. But nonetheless it does seem to be a new issue, so it may well be a bug too, and no matter what it should be fixed. On the other hand, I know that I and many others run quite a few applications that have never ever encountered this issue. That has certainly contributed to my not forcing myself to have to find the time to look into this, and unfortunately I just am not getting things done that I would like to do, including finishing already started stuff.

At one time I believed that I just needed to change my job situation, as the one that I was at had grown to expect too much of my time. About the time I changed jobs my wife changed positions and started working a very very early morning shift. I thought I would adapt but I never did, and she has now found a more normal position. So now I find that my current job is not expecting too much, and my home life has finally gotten mostly back to normal, but I am so far behind on what I want to do on my own that its gotten depressing. Meanwhile its been so long since I've had free time that I've been enjoying spending it in other ways, which just adds to my delays.

That's probably not what you were asking for when you asked me to comment, but I hope it does clarify where I am at. I believe I was always clear from the beginning that my ORMapper was something that I found useful for myself, and that was why and remains why I created it. Of course instead of sharing my code for free I charged $50, but that was always because I felt it was a significant amount of code, and not because I was trying to become a software vendor. I think most people have understood this and not expected to much, and to that end I've actually went far beyond that in my upkeep of the ORMapper, even better than some real vendors if I dare so.

Unfortunately that may have created the impression that I was always going to make this my priority, but as much as I sometimes want to, that simply is not and cannot be my reality. So while I do still hope to make the time to make another official release, including this bug fix, I'm also very happy to see that Rob has apparently fixed it since I haven't found the time. In the meantime, I hope that you and others continue to find the ORMapper to be useful once you get this bug fix in place, as I know I and many others have. I do hope to either update it for Linq, or if Linq is good enough then I want to update my Portal to Linq -- whatever I find useful myself again, and hopefully others will agree.

I should stop myself now. :)

Thanks, Paul Wilson

Error during rollback/Zombie message

Wed, 18 Apr 2007 15:32:40 GMT

Strike!

The fix works. Whereas with the old version we could reproduce the zombie within several thousand saves, with the fix in place it didn't occur after one million.

By the way, the error seemed always to occur more often on heavily memory and cpu constrained systems (not on our development systems). After seeing the patch i can now imagine why.

Thanks again,

Gunter

Error during rollback/Zombie message

Fri, 13 Apr 2007 02:18:19 GMT

We were seeing this error from time to time and a couple weeks ago I came across this thread and updated the code as described. We haven't seen the issue since. Hopefully you'll have the same experience, and hopefully the fix will make it's way into the next release. :)

Cheers,
Steve
http://iqueryable.com/

Error during rollback/Zombie message

Thu, 12 Apr 2007 14:28:18 GMT

Rob,

If this really fixes it, I'll send you over a case of good german beer :)

We discovered/posted this problem already months ago and worked around it just retrying transactions up to three times when we get this zombie error. We were just about to switch to another O/R mapper because of this problem and the feeling it will never be fixed.

We could reproduce the error several times a hour before with a small test program and will test the fix tomorrow and post about our results.

Paul, could you please comment on this?

Regards, Gunter

Updating Table

Mon, 09 Apr 2007 08:27:34 GMT

Thanks for the reply - it was a typo

OPathQuery query = new OPathQuery(typeof(PerryWorld.Productfolio.BusinessObjects.TblCompany), "CompanyId == 123");

I'm still getting the same problem.

Cheers
Rich

Updating Table

Sun, 08 Apr 2007 22:14:47 GMT

Hi There, I'm not sure you if typed the code or done a copy/paste but you are missing a closing parenthesis after "CompanyId == 123" to close the OPathQuery class Constructor.

it probably should be:

OPathQuery query = new OPathQuery(typeof(PerryWorld.Productfolio.BusinessObjects.TblCompany), "CompanyId == 123");

Updating Table

Sun, 08 Apr 2007 10:19:59 GMT

Hi,
We have a simple table that we are trying to update as follows :

OPathQuery query = new OPathQuery(typeof(PerryWorld.Productfolio.BusinessObjects.TblCompany), "CompanyId == 123";

PerryWorld.Productfolio.BusinessObjects.TblCompany company = (PerryWorld.Productfolio.BusinessObjects.TblCompany)Manager.Engine.GetObject(query);

company.TrialVersion = "N";

company.TrialPeriod = 0;

Manager.Engine.StartTracking(company, Wilson.ORMapper.InitialState.Updated);

Manager.Engine.PersistChanges(company, PersistDepth.SingleObject);

But we get an error saying "Line 1: Incorrect syntax near ';'."

Any help would be appreciated

Thanks
Rich

The passed arrays are different lengths

Sun, 01 Apr 2007 00:23:37 GMT

It looks like the same thing again. You're going to have to have a composite key definition in your relationship. That means in your case 2 members and 2 fields -- not just one of each.

Thanks, Paul Wilson

The passed arrays are different lengths

Sun, 01 Apr 2007 00:21:16 GMT

Ok, Thanks Paul, this problem was solved but I have a new problem with another 2 tables and I can't see what's wrong :-S

the message is the same:

The passed arrays are different lengths. This may indicate a problem with the mapping for entity 'GTrafico.Data.TITINERARIO'.

The tables

TPROGRAMA

IDPROG (PK)

NUMODO (PK)

ETC....

TITINERARIO

NSITINE (PK)

IDPROG (PK, FK)

NUMODO (PK, FK)

MASCARA (PK)

FEINI (PK)

ETC...

The code that fails:

Dim keys(1) As Object

keys(0) = "5654/4"

keys(1) = 6

Return Global.Manager.GetObject(GetType(TPROGRAMA), keys)

and the mapping file

Do you see the problem?

Thanks for your time ;-)

The passed arrays are different lengths

Wed, 28 Mar 2007 16:22:42 GMT

Hi Wilson, I have solved the previous problem!

The right line is

and the same with mapping for TITINERARIO.

We are using Welter templates 3.1 and I think this it is a bug. It generates one relation for each foreing key, without looking if thoose foreing keys are composite.

I also have to delete the additional IList from each class

Private _tITINERARIOList2 as IList

Ok, I have undesrtand the problem.

Thanks Wilson. A great tool.

PD:I hope you see this post before wasting your time answering the previous one :-S

Issue with large numbes of database connections.

Mon, 26 Mar 2007 19:16:15 GMT

Any word on this? <BUMP>

Issue with large numbes of database connections.

Mon, 26 Mar 2007 19:15:52 GMT

Oops, wrong link -- try this one instead.

Issue with large numbes of database connections.

Mon, 26 Mar 2007 19:12:08 GMT

See this thread.

Error during rollback/Zombie message

Mon, 26 Mar 2007 19:11:06 GMT

We encountered the same random Zombie. A few months ago, we opened a support incident with Microsoft. After many (many...many...many...) hours of troubleshooting, researching, escalating, and finger pointing, Microsoft finally conceded that this is a bug with ADO.Net. In specific, it's a bug with the SqlTransaction object. It will be fixed in a "future version" of ADO.Net, but a hotfix will not be issued since this is an "obscure scenario with a simple workaround."

I won't bore you with details, just a fix.

Don't use the SqlTransaction's Connection property.

Check the source code for the ORMapper and you'll find that Internals.Connection.GetTransaction connects to the database, begins a transaction and returns the IDbTransaction. The calling method (the Transaction constructor) then assigns an internal reference to the IDbTransaction's Connection property. What we found was that every once in a while, the IDbTransaction's Connection was NULL!!!! This ended up to be the root of the Zombie issue, which manifested itself later when we called PersistChanges.

The reason the Connection was NULL is really quite odd. In ADO.Net 2.0, the SqlTransaction was modified so that it has two references to the SqlConnection used to create it. The first is the publicly exposed Connection property. The second in a private connection property. The private connection has a weak reference to the public connection.

Since the SqlConnection is created inside Internals.Connection.GetTransaction, it goes out of scope when the IDbTransaction is returned to the Transaction's constructor. At that point, the Connection is eligible for Garbage Collection. Every once in a while, the GC collects the Connection object between the point the Transaction is created and the point you PersistChanges.

We fixed this using the following code:

1) Modify the constructor of the Transaction class:

            internal Transaction(Context context, IsolationLevel isolationLevel) {
                  this.context = context;
                  //in .NET 2.0 is to keep a reference to the outer connection of the transaction
                  //
                  //OLD CODE
                  //this.transaction = this.context.Connection.GetTransaction(isolationLevel);
                  //this.connection = this.transaction.Connection;
                  //
                  //NEW CODE
                  this.connection = this.context.Connection.GetConnection();
                  this.transaction = this.connection.BeginTransaction( isolationLevel );
                  this.context.Connection.InterceptCommand(this.id, null, CommandInfo.BeginTran, null);
         }

2) Modify the Internals.Connection class

a. Remove the GetTransaction( String isolationLevel ) as it will no longer be referenced

b. Add new method GetConnection() which will return a connection to the database:

            internal IDbConnection GetConnection()
            {
                  IDbConnection connection = ProviderFactory.GetConnection(this.connection, this.provider);
                  connection.Open();
                  return connection;
            }

Happy Hairpulling,

Rob

ORM error transaction has completed

Mon, 26 Mar 2007 19:09:45 GMT

Yes and no. There is some code that tries to account for an esoteric error that's internal to ADO.NET and which typically only occurs in high volume situations. But it seems that while I reduced the frequency of this issue for some, others have occasionally continued to run into this. My only repros of this occurred without the mapper involved also, which is how I determined it was an internal ADO.NET error, and some customers I worked with concluded the same thing. But since it has since raised its head again, and some have now said that this does not occur without the mapper, I can no longer make a promise that its fixed in every case. But it is fixed for every case that I have been able to repro, and I have not seen this occur in my own applications.

Thanks, Paul Wilson

ORM error transaction has completed

Mon, 26 Mar 2007 19:04:46 GMT

We are currently at the 3.0 version of the ORM tool. Is there a fix in later versions that might eliminate the following error that we get on occasion?

2007-03-08 10:27:41,460 [4616] ERROR log4net.Appender.FileAppender [] <> - This SqlTransaction has completed; it is no longer usable.

The passed arrays are different lengths

Mon, 26 Mar 2007 19:04:31 GMT

Your TASIGNACION object has relationships with your TCONCESION object, and since the TCONCESION object has a composite key with 2 fields then those relationships must also be mapped with the field element representing that same composite relationship. Similarly with the reverse relationships -- basically once its composite everything has to be setup the same way that relates to it.

Thanks, Paul Wilson

The passed arrays are different lengths

Mon, 26 Mar 2007 19:00:35 GMT

Hello,

I have bought WilsonOR and I am in the same situation.

I have 2 involucred tables. TASIGNACION and TCONCESION

TCONCESION

IDCONCE (PK)

NSEMPRE (PK)

ETC....

TASIGNACION

NSLINEA (PK)

FEINI (PK)

IDCONCE (PK)

NSEMPRE

ETC.....

My mapping is like follows

And the code that fails

Dim keys(1) As Object

keys(0) = original_IDCONCE

keys(1) = original_NSEMPRE

Dim concesion As TCONCESION = [Global].Manager.GetObject(GetType(TCONCESION), keys)

Message "The passed arrays are different lengths. This may indicate a problem with the mapping for entity 'GTrafico.Data.TASIGNACION'." String

any suggestions?

Thanks

long-running apps

Tue, 20 Feb 2007 16:57:40 GMT

I have a long-running application, a Service really, and currently the architecture is a little funny. One thread is started by the service. it checks some config settings in my db, and then starts up N worker threads based on that config data. Those N Worker threads then each look at a schedule. Generally schedules are set to fire once a day at a specific time. the worker threads then put themselves to sleep until that time will happen. so if it's 4pm they go to sleep until perhaps 9am the next morning. Then when they wakeup they do some work, and go back to sleep for 24 hours. When this happens the entire app might be dormant for those 24 hours, because most of the threads do their work in the mornings. My first error happened when I tried to save changes to an object I had created 16 to 24 hours before. I fixed this problem by using the key value of the object that i had created, and using the Mapper to create a new instance, then making the change to that instance and saving that one, and not working with the "stale" instance of the object. Well, now I'm getting a much more difficult error. I'm seeing the errors reported in this thread. But the problem is that it is definately not 1 out of every 100000 calls. I make maybe 10 to 20 "save" calls a day, and this is happening every day. Of course it happens from a different spot in the code every time, just somewhere that I'm using the ORMapper to persist some changes, and the really tough thing is that even though I am calling the code on a worker thread, which has a try catch block around its starting call, when the error is thrown, it causes all threads, the starting thread and all created worker threads, to abort. Could my architecture have anything to do with it? is there some shared objects that are crashing all my threads?

Nullable Date Error

Mon, 19 Feb 2007 21:13:26 GMT

Do you have any other ideas on this Paul? We're currently having to recode large portions of a project due to this error, any help would be appreciated.

Thanks

Adam

Nullable Date Error

Thu, 15 Feb 2007 15:38:39 GMT

Thanks for your reply Paul.

I don't have any nullValue="" settings in my mappings.config, a sample date attribute would be -

<attribute member="_invoicesent" field="invoice_sent" alias="Invoicesent" />

Which is basically the same as it is in the working project I have.

Nullable Date Error

Thu, 15 Feb 2007 14:48:25 GMT

Make sure you remove any nullValue="..." setting you have for these fields in your mapping file. That was the non-generic, pre-.net 2.0, way to handle nulls, using "magic" numbers, and if its there in your mapping file then it means the mapper will still try that technique, which will break your nullable types.

Thanks, Paul Wilson

Nullable Date Error

Wed, 14 Feb 2007 22:54:10 GMT

I have several datetime database fields which accept nulls, I have changed these members to nullable (of date) in the appropriate class but get this error whenever I retrieve a record that contains a date:

[InvalidCastException: Invalid cast from 'System.DateTime' to 'System.Nullable`1[[System.DateTime, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]'.]
   System.Convert.DefaultToType(IConvertible value, Type targetType, IFormatProvider provider) +864
   System.DateTime.System.IConvertible.ToType(Type type, IFormatProvider provider) +36
   System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider) +433
   Wilson.ORMapper.QueryHelper.ChangeType(Object value, Type type) +334
   Wilson.ORMapper.Internals.Instance.SetField(EntityMap entityMap, Object entityObject, String member, Object value, CustomProvider provider) +49
   Wilson.ORMapper.Internals.Instance.SetObject(IDataRecord data) +316
   Wilson.ORMapper.ObjectReader.Read() +251
   Wilson.ORMapper.Internals.Context.GetObject(Type objectType, Object objectKey, Boolean firstLevel) +268
   Wilson.ORMapper.ObjectSpace.GetObject(Type objectType, Object objectKey) +66
   admin_test.Page_Load(Object sender, EventArgs e) +54
   System.Web.UI.Control.OnLoad(EventArgs e) +80
   System.Web.UI.Control.LoadRecursive() +49
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3743

I've tried everything I can think of but am unable to get this to work. Strangely, I have another project using WORM with datetime fields which I handle in exactly the same way and that one works fine.

Any ideas?

keyType="Auto" for string

Fri, 02 Feb 2007 22:17:08 GMT

I'm not really intentionally trying to support any Auto type beyond ints, but there is some code there that others have supplied to try to achieve something beyond ints. I'm not real sure exactly what those cases are, although I would think maybe database-created Guids might be one of those cases, but I'm just guessing.

As for the decimal stuff you're seeing, that should only occur in the Oracle path, and its a requirement for Oracle since Oracle doesn't have any native int concept, so I have to convert decimals to ints. There may be a way to change the Oracle code-path to work with strings also, but again its not something I've ever worked with.

Thanks, Paul Wilson

keyType="Auto" for string

Fri, 02 Feb 2007 22:12:35 GMT

Hi,

I am running 4.2.2.0 and having a problem with an keyType=”Auto” if the key is a string. I see that it is supported in EntityKey.cs line 148… but then there is an error when the INSERT runs because line 300 in Connection.cs assumes a Decimal return value. I haven’t downloaded 4.2.2.1, but the notes don’t say anything about this issue. Am I doing something wrong? I have seen a few posts where people were using a string key, but its not clear that they got it to work?

Thanks!

IObjectNotification event not firing

Fri, 02 Feb 2007 22:11:30 GMT

Hmmm, I can't think of any reason why OnDeleting would not be working for basic cases -- you'll need to send me something to reproduce it, and then realize I'm running very short on time lately. As for ExecuteDelete, all of the Execute methods are intentionally designed to be "batch" sql operations, so they do not work on individual objects, which means there are no events that I can expose.

Thanks, Paul Wilson