I'll reply to the two halves of this message separately. > I'm sorry, but I don't like to do it the way FlexWiki does... > > I much prefer the way we do it with Qasper. Qasper can use any kind of > database, from Access to mySQL, Oracle or SQL Server. We aren't reliant > on the built-in SQL Server support functionality in .NET (which, by the > way, I didn't even know .NET supported. Even if I did, I wouldn't stray > from the way we do it because our way is the way db setups have been > done since time began, I think). > > I think it's a mistake to use such restrictive built-ins. It requires > special functionality on the server as I see it and that's probably the > problem with our installations. > > And, I didn't know you had to run an EXE to set up FlexWikiSqlStore. So > therein likely lies the problem...
Generally speaking, I agree with you. I think we should supply a database script that can be run as-is. I very nearly ditched the EXE in favor of that approach, but at this stage I'm trying not to change things that don't *need* to be changed. Also, I've learned that different people have different preferences. Some people like the GUI. Fortunately, the SQL script is available in the source distribution. It probably needs to be tweaked very slightly to remove some parameters - I'm guessing the change is to two or three lines at most - but then it should work just fine. One thing I would mention is that all your namespaces can go in just one database. So the database setup is actually a once-per-wiki thing. On the question of supporting databases other than SQL Server: I agree that it's a good idea. I even made some changes when I was updating it to make that sort of thing much easier to support in the future. So if someone wants to donate some time to making it happen, that would be great. Perhaps your company, which is using FlexWiki in a commercial product, would be kind enough to pay for someone's time to do so - that always makes things go a lot faster. Unfortunately, I will not be the one adding this in. My list of changes is already far too long, and at this point in the 2.0 release lifetime I need to refrain as much as possible from adding new features for the sake of my own sanity. > Re: permissions. I set all the permissions, from the top folder in > FlexWiki all the way down as full permission: RWXD so I think it must > be something else... There are two types of permissions: file permissions and database permissions. Database permissions are set via a tool like SQL Server Management Studio or via direct SQL statements such as "GRANT USER ...". The error in your log appears to be a *database* security problem, not a filesystem security problem. Of course, if you never created a database, that's even more likely to be it. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Flexwiki-users mailing list Flexwiki-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flexwiki-users
