Quoting Stefan Hornburg (Racke) (suppressed): > > > However, I think IC has to address this issue in order to avoid > > > serious and unexpected data loss. > > > > > > > I have never heard of this problem before, but unless we get more > > information surrounding the issue there will be no chance to fix > > it. > > Forgot this link: > > http://mail.pm.org/pipermail/spug-list/2004-December/006143.html Since we do a disconnect(), this shouldn't pertain. Also, I wonder how a table is getting put in AutoCommit=0 unless you specifically enable that or do a [flag type=transactions ...]. Of course if you have orders set up to do transactions, that will happen upon an order. But a rollback should be done. > > > > > I have to some extent lost patience with Postgres and DBD::Pg, as > > it seems to have constant little problems that change from version > > to version of each. > > Hehe. I also feel that Postgres more cumbersome to deal with for > web apps. I am sure Postgres is great for a lot of things, but I don't find it too stable with regard to implementation. Typically once something works on MySQL it keeps working (their recent change in mysqldump format notwithstanding). With Postgres, upgrades are fraught with danger, as things will just stop working and require a fire drill to either revert or convert the data. -- Mike Heins Perusion -- Expert Interchange Consulting http://www.perusion.com/ phone +1.765.647.1295 tollfree 800-949-1889 <suppressed> I don't want to get to the end of my life and find I have just lived the length of it. I want to have lived the width of it as well. -- Diane Ackerman _______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.