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
|
I tried to setup SQLite to use with Lightspeed but I get error message, Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information. I'm using SQLite dll from "provider" folder but no go. I attached a sample project. I appreciate if you can tell me what I'm doing wrong. Thanks. -chris ps. "Upload a file" below doesn't work. I'll try to upload later but I hope you can tell from the message above. |
|
|
"Upload a file" didn't work from Explorer but works from FireFox. Here we go. |
|
|
This is a delightful 'feature' of .NET 4.0 when loading DLLs -- such as SQLite -- which contain a mixture of native (C/C++) and .NET code. To get rid of the error, add http://stackoverflow.com/questions/4311274/visual-studio-adding-dll-as-reference-error |
|
|
Hi, Ivan, Good to have you back. ^^ Yeah, it works beautifully. I need a client db to store temporary information locally and needed a light weight db. While trying to get Sqlite to work, I tried SQL Server CE. It seems to work fine also. It seems I have two choices for the light weight db, Sqlite or SQL CE. Since ORM is never straight forward, there might be some unknown problem laying ahead. If I may ask, from your experience what is your recommendation on the choice? I suppose you abstract the differences and there are the same functionally, then, how about administrations? Performance will not be important, in this case. FYI, I use MySql on the server side, so compatibility (migrating data back and forth) will be a factor. Thanks. -chris |
|
|
Between SQLite and SQL CE, I'd probably go for SQLite. SQLite supports most queries, whereas SQL CE has some quirks and limitations which may result in seemingly valid queries being rejected at runtime. (To be clear, both have quirks and limitations, but SQL CE has more.) But for many applications the differences won't matter, and SQL CE may have advantages in other areas. On the admin side, SQL CE has slightly better graphical tooling, but lacks scripting. I don't think either of them has particular MySQL migration support. |
|
|
Great! and thanks for the tip. I'm under quite a bit of pressure implementing Undo and it keep my head spinning... I'll have to support undo both at db level as well as memory level. I appreciate for your support. -chris |
|
|
I just switched from SQL CE to SQLite. From the Model Editor, adding an association and updating Data Base causing the following error.
Is this expected? It seems pretty severe limitation. Thanks. -chris |
|
|
Ah, yes, I forgot about that... sorry... SQLite has very limited support for foreign keys. You can specify a foreign key when you create a table, but you can't add a foreign key to an existing table. This isn't really a limitation when it comes to run-time, because the ORM will update IDs for you even if the database doesn't check integrity. But it does affect the designer when it comes to adding associations to existing entities. |
|
|
Hmm.. it seems to be a show stopper. There must be a reason why they don't allow adding foriegn keys but I don't have luxury to play with it. I'll just go back to SQL CE for now. Thanks. -chris |
|