© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Message-ID: <email address hidden>
Date: Mon, 19 Sep 2005 17:48:23 +0200
From: Johan Palmqvist <email address hidden>
To: <email address hidden>
Subject: Re: Bug#329065: [php-maint] Bug#329065: php5-sybase: sybase_ct doesn't
always return correct results from MS SQL
-------
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-
Acknowledged, I just considered it "data loss" due to another
application which relies on correct results in order to correctly save
some data, but I get your point.
However, getting wrong results could theoretically, depending on the
application, cause real data loss when doing delete queries using a
previous bad result as input. But I admit that's a bit far fetched. :)
I was also thinking that packaging of both modules as php5-sybase and
php5-mssql, maybe with some warning notification during installation
about possible issues with MSSQL, could be a good temporary workaround.
The long term solution is to migrate away from MSSQL but our mission
critical applications would most likely take years to migrate, test and
deploy.
Thanks
/ Johan
Ondrej Sury wrote:
>
>Thanks for that test case.
>
>Just a quick explanation what "data loss" mean (at least to us). To
>mark this bug as grave because of "data loss" it would have to delete
>affected data from database.
>
>I know that this is annoying bug (at least for you) and we will work
>with upstream to resolve it, but it's not "grave" bug, because you are
>using very rare setup (php on linux with MSSQL) and it doesn't happen on
>all occasions.
>
>O.
>
>
-------
Content-Type: text/html; charset=ISO-8859-1
Content-
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content=
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Acknowledged, I just considered it "data loss" due to another
application which relies on correct results in order to correctly save
some data, but I get your point.<br>
<br>
However, getting wrong results could theoretically, depending on the
application, cause real data loss when doing delete queries using a
previous bad result as input. But I admit that's a bit far fetched. :)<br>
<br>
I was also thinking that packaging of both modules as php5-sybase and
php5-mssql, maybe with some warning notification during installation
about possible issues with MSSQL, could be a good temporary workaround.<br>
<br>
The long term solution is to migrate away from MSSQL but our mission
critical applications would most likely take years to migrate, test and
deploy.<br>
<br>
Thanks<br>
/ Johan<br>
<br>
<br>
Ondrej Sury wrote:
<blockquote <email address hidden>"
type="cite">
<pre wrap=""><!---->
Thanks for that test case.
Just a quick explanation what "data loss" mean (at least to us). To
mark this bug as grave because of "data loss" it would have to delete
affected data from database.
I know that this is annoying bug (at least for you) and we will work
with upstream to resolve it, but it's not "grave" bug, because you are
using very rare setup (php on linux with MSSQL) and it doesn't happen on
all occasions.
O.
</pre>
</blockquote>
</body>
</html>
-------