This project is read-only.

Invalid column names error when going to Admin tab

Apr 4, 2009 at 1:11 PM
Checked out latest version, launched solution in VS, entered admin credentials and when clicking on Admin tab getting a SQL error saying following columns do not exist.
(BTW this is the MDF database that sits in App_Data folder, had no success creating new DB with supplied scripts.)
What I had to do is attach the MDF to SQL Express in SQL Express Management studio, then manually add the missing columns like so:

ALTER TABLE [dbo].[oxite_Comment]
Add [CreatorName] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL

ALTER TABLE [dbo].[oxite_Comment]
Add [CreatorEmail] [nvarchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL

ALTER TABLE [dbo].[oxite_Comment]
Add [CreatorHashedEmail] [nvarchar] (200) COLLATE SQL_Latin1_General_CP1_CI_AS NULL

ALTER TABLE [dbo].[oxite_Comment]
Add [CreatorUrl] [nvarchar] (300) COLLATE SQL_Latin1_General_CP1_CI_AS NULL

Question: why do I need to do this and what other columns I miss that I don't know about?
Apr 7, 2009 at 6:50 AM
We do our development using DB Pro and manually update the MDF as we can remember to when we make changes to the schema.  We will always ensure that the schema is correct for every release, but can't promise it will always be right for the latest checkin.  That said, usually when people (like you) bring it up, we'll update the MDF for those checking out the latest code.  I just now updated the MDF to the latest schema so if you grab it you should be good to go.  Most of the time, we will not update the SQL scripts until the new release since it's even more of a manual process, FYI.
Apr 7, 2009 at 2:32 PM
Thanks so much!