Re: [asterisk-dev] Postgres Realtime driver
William Lloyd wrote: From a long term development point of view should we just be focusing on ODBC and removing all the native drivers altogether? What's the performance impact of ODBC vs native? (Is that extra layer negligible for most common tasks?) Has anyone ever noticed a difference or ran any benchmarks? In general as long as the benefits are there and it's stable (or eventually will be) I'm all for a native Postgres driver. I've been given the task of migrating some * boxes from MySQL to Postgres and hopefully I'll have more feedback here soon as to the results. (specifically the postgres driver) Cheers, C. begin:vcard fn:C. n;quoted-printable:Bergstr=C3=B6m;Christopher email;internet:[EMAIL PROTECTED] tel;work:+1 206-973-3178 tel;fax:+1206-312-5233 url:http://www.NetSyncro.com/ version:2.1 end:vcard ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Postgres Realtime driver
Well, Apart from the ODBC or not ODBC discussion you haven't given me a lot of feedback on the actual driver... Any thoughts on that? Any experiences? /O ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Postgres Realtime driver
From a long term development point of view should we just be focusing on ODBC and removing all the native drivers altogether? IE even for MySQL.. I use postgres instead of MySQL nowadays but I use ODBC to get there. -bill On 4-Apr-06, at 11:54 AM, Olle E Johansson wrote: Friends, Time to make a decision on the realtime PostgreSQL driver As I have no experience of Postgres, I need some feedback: - What problem does it solve that can not be handled by using ODBC to postgreSQL? - This driver is based on the mysql realtime driver, which is known to cause a lot of problems. Will this happen here too? Any testing experience? - Are there enough developers out there to maintain this driver? We don't want to get stuck with code that is not maintained... I am playing devil's advocate here, so please give me some reasons to either say thanks, but no thanks or committed as a last entry in the bug report. Issue #5637 in the bug tracker. /Olle --- * Olle E. Johansson - [EMAIL PROTECTED] * Asterisk European Tour: http://www.meetasterisk.com ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Postgres Realtime driver
On Tuesday 04 April 2006 15:00, [EMAIL PROTECTED] wrote: DBLib for some operations. The big advantage to ODBC is the software you write can be made to work with any RDBMS backend that has an ODBC driver (which is about all of them) without ANY change to the software. Also, a In an ideal world, yes. But RDBMSes have slightly different ways of wanting things worded, some may run faster if you order them in a particular way and so on... It's good to code as flexibly as possible but sometimes you need to go around the driver or the SQL95 conformance to get something done better. -A. ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Postgres Realtime driver
On 17:07, Tue 04 Apr 06, Andrew Kohlsmith wrote: In an ideal world, yes. But RDBMSes have slightly different ways of wanting things worded, some may run faster if you order them in a particular way and so on... It's good to code as flexibly as possible but sometimes you need to go around the driver or the SQL95 conformance to get something done better. My idea. We have some apps that work with MySQL, Postgres and MS-SQL. We gave up the ODBC stuff and coded our own database lib that uses the native 'drivers'. I'm no fan of ODBC, it limits you too much. (imho) -- Michiel van Baak [EMAIL PROTECTED] http://michiel.vanbaak.info GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x7E0B9A2D Why is it drug addicts and computer afficionados are both called users? ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Postgres Realtime driver
4 apr 2006 kl. 21.00 skrev [EMAIL PROTECTED]: What's the performance impact of ODBC vs native? (Is that extra layer negligible for most common tasks?) Has anyone ever noticed a difference or ran any benchmarks? We use PostgreSQL with an ODBC driver for commercial apps (non- *) and have found the performance to be fine. I don't know about PostgreSQL specifically, but don't assume that ODBC means extra layer. A great many of the ODBC drivers out there are single layer and therefore have no more overhead than the native method of access. I know MS SQL Server is that way. MS says that ODBC access to SQL Server is at least as fast as DBLib, and our benchmarks bear that out. ODBC is, in fact, faster than DBLib for some operations. The big advantage to ODBC is the software you write can be made to work with any RDBMS backend that has an ODBC driver (which is about all of them) without ANY change to the software. Also, a lot of people think of ODBC as an MS thing when in fact it is just an implementation of the X/Open CLI (Call Level Interface) specification which is determined by an independent standards body. Well, that's the marketing glorified message. Our experience with the FreeTDS problems show that regardless of ODBC, we have to adopt to the underlying layer anyway and have db-specific code in there. /O ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
RE: [asterisk-dev] Postgres Realtime driver
From a long term development point of view should we just be focusing on ODBC and removing all the native drivers altogether? IE even for MySQL.. I don't mind Realtime moving to ODBC completely, but I would hate to see the MYSQL (and PGSQL or whatever it is called) apps be completely removed. -- Andreas Sikkema BBned NV Software EngineerPlaneetbaan 4 +31 (0)23 70743422132 HZ Hoofddorp ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Postgres Realtime driver
What's the performance impact of ODBC vs native? (Is that extra layer negligible for most common tasks?) Has anyone ever noticed a difference or ran any benchmarks? We use PostgreSQL with an ODBC driver for commercial apps (non- *) and have found the performance to be fine. I don't know about PostgreSQL specifically, but don't assume that ODBC means extra layer. A great many of the ODBC drivers out there are single layer and therefore have no more overhead than the native method of access. I know MS SQL Server is that way. MS says that ODBC access to SQL Server is at least as fast as DBLib, and our benchmarks bear that out. ODBC is, in fact, faster than DBLib for some operations. The big advantage to ODBC is the software you write can be made to work with any RDBMS backend that has an ODBC driver (which is about all of them) without ANY change to the software. Also, a lot of people think of ODBC as an MS thing when in fact it is just an implementation of the X/Open CLI (Call Level Interface) specification which is determined by an independent standards body. Glenn Lawler ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Postgres Realtime driver
On Tue, Apr 04, 2006 at 05:54:10PM +0200, Olle E Johansson wrote: OEJ - What problem does it solve that can not be handled by using ODBC to OEJ postgreSQL? Speed. Stability. OEJ - This driver is based on the mysql realtime driver, which is known OEJ to cause a lot of OEJ problems. Will this happen here too? Any testing experience? OEJ - Are there enough developers out there to maintain this driver? We OEJ don't want OEJ to get stuck with code that is not maintained... I'm not test this code and wait for end work for it. If it is needed -- I can test it, and start to code review. -- JID: [EMAIL PROTECTED] ICQ: 58417635 (please, use jabber, if you can) http://freesource.info/ ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
