BugNET

Open source issue tracking & project management
| Login

Import Update!

We are currently in transition and have moved our discussions to CodePlex. These forums will remain as reference until we launch of our new site in the upcoming weeks. After that they will be removed.

Thank you for your patience during our transition.

Forums

HomeHomeSupportSupportInstalling BugN...Installing BugN...problems in sql script (collation) + installation stops without error msgproblems in sql script (collation) + installation stops without error msg
Previous
 
Next
New Post
1/19/2007 9:38 AM
 
Hello,

I'm trying to install the latest bugnet v0.7 (with a DB schema version 0.7.719.0) but I've many errors while having the install.aspx page running the aspx page.

My DB is set to a Latin_binary collation, and there are many locations in scripts where the case of table and field names change (ex: Username and UserName, RoleName and Rolename, plenty of xxxID versus xxxId ...). I first tried to recreate my database with collation insensitivity, but that raises other SQL errors. I also corrected the collation problems in the scripts, but then I get

Installing BugNET
Version: 0.7.719.0

Installation Status Report

Installing Version: 0.7.719.0
Installing Membership Provider... - 00:00:00.1402016
Installing BugNET Database... - 00:00:02.2632544
Installing BugNET Default Data... - 00:00:03.2546800
Creating Administrator Account... - 00:00:03.5651264

And then nothing... And if I go to the main page, it's blank... (There is a similar problem mentioned in another post, but contrary to that post, my connection string in web.config looks fine:

    <add name="LocalSqlServer" connectionString="Data Source=(local);Initial Catalog=BugNet;user=test;password=test;Persist Security Info=True" />

and the one in Log4Net.config:

<connectionString value="Data Source=(local);Initial Catalog=BugNet;user=test;password=test;Persist Security Info=True" />


Any idea? Please, I really would like to try BugNet!

Cheers
Chris
 
New Post
1/19/2007 10:23 AM
 
Well, there were just similar casing issues in stored procedure. That's it now. It works.

But may I strongly advise to the development team to rationalize their use of upper and lower case in the naming of sql "objects"? I may send my updated scripts if you want (just give me an email to send them). Mixing case in SQL object is really a bad practice...

Cheers,
Chris
 
New Post
1/19/2007 3:44 PM
 
Thank you for your insight on this problem, I will add it to the issue tracker so that we may address this issue in the future.  Please feel free to email the script to admin@ nospam.bugnetproject.com    please remove the nospam. :)

Davin Dubeau

follow us on twitter facebook users group google plus
 
New Post
6/21/2007 6:22 AM
 

Hi David,

 

I've just tried to install the latest version (7.832) to a new platform and got three script errors due to casing (my DB's collation is still in case-sensitive mode...).Here are the 3 things to correct in BugNEt.Schema.SqlDataprovider.cs:

  • line 458: @ProjectID --> @ProjectId
  • line 1179: @BugCommentID --> @BugCommentId
  • line 1284: @IssueTypeID --> IssueTypeId

I have another bug due to collation when running InstallRoles.sql but I cannot solve it (it does not appear to be blocking... ???).

 
New Post
6/21/2007 2:29 PM
 

Thanks I will fix those up.

The InstallRoles.sql is apart of the microsoft membership provider, I am not to sure what could be causing an error in that script.


Davin Dubeau

follow us on twitter facebook users group google plus
 
Previous
 
Next
HomeHomeSupportSupportInstalling BugN...Installing BugN...problems in sql script (collation) + installation stops without error msgproblems in sql script (collation) + installation stops without error msg


Forum Policy

These Discussion Forums are dedicated to the discussion of the BugNET issue tracker.

For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:
1. No Advertising.
2. No Flaming or Trolling.
3. No Profanity, Racism, or Prejudice.
4. Site Moderators have the final word on approving/removing a thread or post or comment.
5. English language posting only, please.