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
|
We are using lightspeed for a type of CMS, and we need to be able to handle long strings (ie SQL TEXT datatype). What do you need to do with your lightspeed model to do this. The designer does not have anyway to specify a SQL datatype other than a NVARCHAR. This will be unfortunatly be a showstopper for us... |
|
|
|
|
Hello Tim, Just want to clarify what the issue is here. At runtime, a TEXT column maps to a string property, so there should be no issue there (if there is, let us know and we will look into it). At design time, we should be able to infer a TEXT column as a string property if you drag the table onto the designer. Again, if that's not working for you, let us know. The only limitation I am aware of is therefore that if you create a string property using the designer, and then do an Update Database, it will always want to create a NVARCHAR(n) rather a TEXT or NVARCHAR(MAX). Is that the issue you're running into, or have I misunderstood or missed something? |
|
|
|
|
Ah that makes sense so we should really avoid the use of the designer? We tried using the designer to import our initial db design, but when using Update Database it tried to convert all the text fields into NVARCHAR fields and then displayed an error stating that the field length was too high.
|
|
|
|
|
We'll take a look at that -- thanks for the problem description. In the meantime, you shouldn't need to avoid the use of the designer altogether if you don't want to. You can still use it to create your model and generate your .NET entity definitions (of course, you can equally well do so in code if you prefer). The only thing you'll want to stay away from is the Update Database command. (I think Update From Source should still be okay though I have not yet tested this.) |
|
|
|
|
Cool thank you |
|
|
|
