You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by ji...@apache.org on 2004/04/02 20:52:44 UTC
[jira] Created: (JAMES-247) James Does Not Work With Oracle DB For Spool Repository
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JAMES-247
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JAMES-247
Summary: James Does Not Work With Oracle DB For Spool Repository
Type: Bug
Status: Unassigned
Priority: Minor
Project: James
Components:
MailStore & MailRepository
Versions:
2.2.0a18
Assignee:
Reporter: Steve Short
Created: Fri, 2 Apr 2004 10:51 AM
Updated: Fri, 2 Apr 2004 10:51 AM
Environment: Windows XP, Oracle 9i
Description:
Oracle does not allow two columns of type 'long' in the same table. The sqlResources.xml file defines message_body and message_attributes as type 'long raw' so James fails during the initialization phase because it cannot create the spool table.
(* I have tried simply substituting blobs but that does not work - the message content is lost passing through James *)
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Resolved: (JAMES-247) James Does Not Work With Oracle DB For Spool Repository
Posted by ji...@apache.org.
Message:
The following issue has been resolved as FIXED.
Resolver: Noel J. Bergman
Date: Tue, 13 Apr 2004 11:09 PM
Patch contributed by Steve Short adds support for Oracle by changing to use Blob column and Blob JDBC type. Also add support for db2.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JAMES-247
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JAMES-247
Summary: James Does Not Work With Oracle DB For Spool Repository
Type: Bug
Status: Resolved
Priority: Minor
Resolution: FIXED
Project: James
Components:
MailStore & MailRepository
Fix Fors:
2.2.0a19
Versions:
2.2.0a18
Assignee:
Reporter: Steve Short
Created: Fri, 2 Apr 2004 10:51 AM
Updated: Tue, 13 Apr 2004 11:09 PM
Environment: Windows XP, Oracle 9i
Description:
Oracle does not allow two columns of type 'long' in the same table. The sqlResources.xml file defines message_body and message_attributes as type 'long raw' so James fails during the initialization phase because it cannot create the spool table.
(* I have tried simply substituting blobs but that does not work - the message content is lost passing through James *)
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Updated: (JAMES-247) James Does Not Work With Oracle DB For Spool Repository
Posted by ji...@apache.org.
The following issue has been updated:
Updater: Vincenzo Gianferrari Pini (mailto:vincenzo.gianferraripini@praxis.it)
Date: Wed, 19 May 2004 4:04 AM
Comment:
New fix committed. Needed because mssql (and possibly other database products) does not work the way we need with getBlob.
Created a new sqlResources.xml element ("dbOptions") that allows control of the desired behaviour for each database product, specifically with the new "dbOption"s "getBody" and "getAttributes". They drive the usage of either getBlob or getBytes, the latter being the default.
The defaults set should be fully backwards compatible (to 2.1.x and 2.2.0ax); only oracle and db2 are set to use getBlob, so no current installation should break, even without modifying SqlResources.xml.
I fully (?) tested the new dbOptions mechanism and the behaviour of mssql. Other db products should be tested now.
Changes:
assignee changed to Vincenzo Gianferrari Pini
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-247?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JAMES-247
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JAMES-247
Summary: James Does Not Work With Oracle DB For Spool Repository
Type: Bug
Status: Reopened
Priority: Blocker
Project: James
Components:
MailStore & MailRepository
Fix Fors:
2.2.0RC4
Versions:
2.2.0RC3
2.1.3
2.2.0RC1
2.2.0RC2
Assignee: Vincenzo Gianferrari Pini
Reporter: Steve Short
Created: Fri, 2 Apr 2004 10:51 AM
Updated: Wed, 19 May 2004 4:04 AM
Environment: Windows XP, Oracle 9i
Description:
Oracle does not allow two columns of type 'long' in the same table. The sqlResources.xml file defines message_body and message_attributes as type 'long raw' so James fails during the initialization phase because it cannot create the spool table.
(* I have tried simply substituting blobs but that does not work - the message content is lost passing through James *)
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Updated: (JAMES-247) James Does Not Work With Oracle DB For Spool Repository
Posted by ji...@apache.org.
The following issue has been updated:
Updater: Noel J. Bergman (mailto:noel@devtech.com)
Date: Tue, 18 May 2004 7:38 PM
Comment:
Schedule fix for the next release candidate.
Changes:
Version changed to 2.1.3
Version changed to 2.2.0RC1
Version changed to 2.2.0RC2
Fix Version changed to 2.2.0RC4
Fix Version changed from 2.2.0RC1
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-247?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JAMES-247
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JAMES-247
Summary: James Does Not Work With Oracle DB For Spool Repository
Type: Bug
Status: Reopened
Priority: Blocker
Project: James
Components:
MailStore & MailRepository
Fix Fors:
2.2.0RC4
Versions:
2.2.0RC3
2.1.3
2.2.0RC1
2.2.0RC2
Assignee:
Reporter: Steve Short
Created: Fri, 2 Apr 2004 10:51 AM
Updated: Tue, 18 May 2004 7:38 PM
Environment: Windows XP, Oracle 9i
Description:
Oracle does not allow two columns of type 'long' in the same table. The sqlResources.xml file defines message_body and message_attributes as type 'long raw' so James fails during the initialization phase because it cannot create the spool table.
(* I have tried simply substituting blobs but that does not work - the message content is lost passing through James *)
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Closed: (JAMES-247) James Does Not Work With Oracle DB For Spool Repository
Posted by ji...@apache.org.
Message:
The following issue has been closed.
Resolver: Noel J. Bergman
Date: Mon, 7 Jun 2004 4:18 PM
Steve Short reported that he "tested #247 on Oracle 9i and DB2 8.1 with no problems experienced." We've also had reports that it works well with MySQL and PostgreSQL.
Closing this as fixed.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JAMES-247
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JAMES-247
Summary: James Does Not Work With Oracle DB For Spool Repository
Type: Bug
Status: Closed
Priority: Blocker
Resolution: FIXED
Project: James
Components:
MailStore & MailRepository
Fix Fors:
2.2.0RC4
Versions:
2.2.0RC3
2.1.3
2.2.0RC1
2.2.0RC2
Assignee: Vincenzo Gianferrari Pini
Reporter: Steve Short
Created: Fri, 2 Apr 2004 10:51 AM
Updated: Mon, 7 Jun 2004 4:18 PM
Environment: Windows XP, Oracle 9i
Description:
Oracle does not allow two columns of type 'long' in the same table. The sqlResources.xml file defines message_body and message_attributes as type 'long raw' so James fails during the initialization phase because it cannot create the spool table.
(* I have tried simply substituting blobs but that does not work - the message content is lost passing through James *)
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org