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 the Update Database for the first time as a means to create a table in a test database from an entity on the visual designer using a nightly build from about a week ago and with SQL Server. This was actually an entity dropped from another table in the production database. At a minimum, I noticed in the new table in the test database: 1) The Id property was not set to an identity column 2) All varchars were nvarchars 3) The varchar(MAX) column was set to varchar(50)
Although I don't expect the visual designer to be able to create a clone, it should at least create enough so that I can do CRUD against it without setting identity columns and the correct sizes of varchar(MAX). The varchar to nvarchar I really don't care about, but that seems like a simple thing to do. The roundtripping is a huge benefit over the LINQ To SQL Designer, so the more useful you can make it the better. Regards, Dave
|
|
|
I am going to bump this up, because I think we need more metadata somewhere that helps LightSpeed properly set the primary key as an identity if necessary as well as choose between varchar and nvarchar,, etc. when at least using SQL Server.
I ran into the varchar(MAX) on another project again. LightSpeed set it as varchar(10) so perhaps I mis-spoke above when I said it was varchar(50).
Any work being done on this for LightSpeed 3.0?
I am guessing the new support for datatypes in SQL Server 2008 will only make this more necessary.
Regards,
Dave
|
|
|
There is work being done on this for LightSpeed 3, which will increase the level of precision and control that LightSpeed gives you over database creation. We will however look at whether we can implement some of this stuff in 2.x -- thanks for the feedback on where you're finding the pain points! |
|