This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
SimpleDB provider throws and error on the select count(*) query that happens before saving a new entity to the database where a property is labeled unique. Either the provider should ignore the unique attribute for simpledb or query for it in a supported manner. I am using lightspeed for copying data from one provider to another (like SQL Azure to SimpleDB) and in the long run like to leave the unique constraint on the entity property. thanks for your hard work |
|
|
|
|
It may not be the count query that is the problem. Here is the query from the debug <SelectExpression>SELECT
|
|
|
|
|
I believe it is the generated <> or <> in the simpledb management tools != works but <> does not let me know what you find |
|
|
|
|
sorry(type-o) <> does not. Let me know what you find |
|
|
|
|
Thanks for letting us know about this. I've implemented a fix which will be included in the 13 July nightly build: let us know if you still see problems. At the risk of stating the obvious, please be warned that unique validations could kill your performance on SimpleDB, because you're going to incur a separate SimpleDB query for every entity that gets validated. This probably isn't a big deal if you're working with small numbers of entities and the process isn't time critical (which I guess replication may not be) -- but just thought I'd mention it. |
|
|
|
