bugphpGroupWare - Bugs: bug #1640, Problems with setup on Windows NT...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #1640: Problems with setup on Windows NT 4.0, MS SQL Server 7.0

Submitted by:  anokiy
Submitted on:  Thu 07 Nov 2002 03:45:58 PM UTC  
 
Item Group: 0.9.14 releaseCategory: API - Setup
Severity: 3 - NormalPriority: 5 - Normal
Status: Wont FixPrivacy: Public
Assigned to: Dave Hall <skwashd>Open/Closed: Closed
Component Version: ZIPOperating System: MS Windows
Reproducibility: Every TimePlanned Release: None
Fixed Release: 

Tue 06 Dec 2005 03:18:13 PM UTC, comment #2:

NT4 has been EOLd by Microsoft, 0.9.14 has been EOLd by us.

closing WONTFIX

Dave Hall <skwashd>
Project AdministratorIn charge of this item.
Sat 09 Nov 2002 09:27:26 PM UTC, comment #1:

Hey anokiy,

We don't have many (if any) site running on SQL Server. Thanks for the info. I will add the patch to cvs in the next few days.

As for the first problem, I will reallocate this to someone else who understand the setup scripts better than I do, once I have added the patch to cvs.

Keep us posted on your progress, we would be greatful if you could help us to imporve our SQL Server support.

Thanks again

Dave Hall <skwashd>
Project AdministratorIn charge of this item.
Thu 07 Nov 2002 03:45:58 PM UTC, original submission:

I found the following two problems:

Errors appeared when setup tried to create the tables in the server. The tables would be created, but when setup tried to insert any values in the tables, validation would fail due to unexpected null values.

The reason is that the database routines assume default ANSI behavior for table creation, and specifically that fields are nullable unless specified otherwise. This is not true for MS SQL 7.0, as the default for new fields is NOT nullable.

This can be changed at the database level by entering the database properties dialog, Options tab, and checking the ‘ANSI NULL default’ property. I would recommend that this is explained in the installation docs, or that the installation routines are changed to eliminate this assumption.

The second error is that, even when the tables were created, the setup routines didn’t detect them. This meant that when the tables finished installing, instead of moving onto the next step, you were redirected to the previous one. Trying to create the tables again gave errors, of course.

The reason for this is in the table_names() function from the phpgwapi\inc\class.db_mssql.inc.php file:

function table_names()
{
$this->query("select name from sysobjects where type='u' and name != 'dtproperties'");
$i = 0;
while ($info = @mssql_fetch_row($this->Query_ID))
{
$return[$i]['table_name'] = $info[0];
$return[$i]['tablespace_name'] = $this->Database;
$return[$i]['database'] = $this->Database;
$i++;
}
return $return;
}

For MS SQL Server 7.0, table objects are not type ‘u’, they are type ‘U’, so it should read like this:

$this->query("select name from sysobjects where type='U' and name != 'dtproperties'");

I will report back if I find any other errors.

anokiy

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 5 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Tue 06 Dec 2005 03:18:13 PM UTCskwashdStatusNone=>Wont Fix
  Assigned toceb=>skwashd
  Open/ClosedOpen=>Closed
Tue 31 Dec 2002 10:53:43 PM UTCskwashdAssigned toskwashd=>NA
Sat 09 Nov 2002 09:27:26 PM UTCskwashdAssigned toNone=>NA

Back to the top


Powered by Savane 3.1-cleanup1