Hi All,
i have made fairly substantial progress in the Oracle port, in
fact I am running up against limitations due to stubs and
unimplemented features.
I have attached a new schema file as I had not updated the Tickets table
(my apologies). There is also one more change in the In DBIx/EasySearch.pm
file:
Routine _DoSearch
Change
# $QueryString = "SELECT distinct main.* FROM " . $self->_TableAliases;
$QueryString = "SELECT main.* FROM " . $self->_TableAliases;
Since all tables have primary keys I believe the DISTINCT clause is
redundant. If I am wrong please let me know.
Functionality that has been tested this week
rt -response
rt -comments
rt -resolve
rt -stall
rt -open
rt -due
rt -show
rt -subject
rt -queue
rt -prio
rt -finalprio
rt -notify
rt -kill
HTH
Dave
Dave Morgan
Senior Database Administrator
Internet Barter Inc. www.bartertrust.com
408-982-8774
The reason for the distinct was that with some queries, it seemed like
a row was matching more than once and we were getting duplicate results.
Do you wanna send me the latest full copies of your hacked up DBIx stuff,
so I can try an integration?
-jOn Tue, Aug 29, 2000 at 01:01:33PM -0700, Dave Morgan wrote:
Hi All,
i have made fairly substantial progress in the Oracle port, in
fact I am running up against limitations due to stubs and
unimplemented features.
I have attached a new schema file as I had not updated the Tickets table
(my apologies). There is also one more change in the In DBIx/EasySearch.pm
file:
Routine _DoSearch
Change
$QueryString = "SELECT distinct main.* FROM " . $self->_TableAliases;
$QueryString = "SELECT main.* FROM " . $self->_TableAliases;
Since all tables have primary keys I believe the DISTINCT clause is
redundant. If I am wrong please let me know.
Functionality that has been tested this week
rt -response
rt -comments
rt -resolve
rt -stall
rt -open
rt -due
rt -show
rt -subject
rt -queue
rt -prio
rt -finalprio
rt -notify
rt -kill
HTH
Dave
–
Dave Morgan
Senior Database Administrator
Internet Barter Inc. www.bartertrust.com
408-982-8774