[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Phpgroupware-tracker] [Bug #1640] Problems with setup on Windows NT 4.
From: |
nobody |
Subject: |
[Phpgroupware-tracker] [Bug #1640] Problems with setup on Windows NT 4.0, MS SQL Server 7.0 |
Date: |
Tue, 31 Dec 2002 17:53:43 -0500 |
=================== BUG #1640: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=1640&group_id=509
Changes by: Dave Hall <address@hidden>
Date: 2003-Jan-01 09:53 (Australia/Melbourne)
What | Removed | Added
---------------------------------------------------------------------------
Assigned to | skwashd | ceb
=================== BUG #1640: FULL BUG SNAPSHOT ===================
Submitted by: anokiy Project: phpGroupWare
Submitted on: 2002-Nov-08 02:45
Category: API - Setup Bug Group: 0.9.14 release
Severity: 5 - Major Priority: None
Resolution: None Assigned to: ceb
Status: Open Component Version: ZIP
Platform Version: Windows Reproducibility: Every Time
Summary: Problems with setup on Windows NT 4.0, MS SQL Server 7.0
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
didnt 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.
Follow-up Comments
*******************
-------------------------------------------------------
Date: 2002-Nov-10 08:27 By: skwashd
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
CC list is empty
No files currently attached
For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=1640&group_id=509
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Phpgroupware-tracker] [Bug #1640] Problems with setup on Windows NT 4.0, MS SQL Server 7.0,
nobody <=