Comments on: Porting Tasks Pro™ to ADOdb http://alexking.org/blog/2005/04/20/tasks-pro-on-adodb Alex King, Denver Web Developer Wed, 23 May 2012 19:06:46 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Ken Scott http://alexking.org/blog/2005/04/20/tasks-pro-on-adodb#comment-4993 Ken Scott Thu, 21 Apr 2005 04:44:41 +0000 http://www.alexking.org/blog/2005/04/20/porting-tasks-pro-to-adodb/#comment-4993 What was the problem with the group by on MS SQL? I know SQL Server supports it (I use it all the time). Is it just a difference in syntax between MySQL and MS SQL? Email me if you would like another pair of eyes to look at the syntax for you. What was the problem with the group by on MS SQL? I know SQL Server supports it (I use it all the time). Is it just a difference in syntax between MySQL and MS SQL?

Email me if you would like another pair of eyes to look at the syntax for you.

]]> By: Ian http://alexking.org/blog/2005/04/20/tasks-pro-on-adodb#comment-4992 Ian Thu, 21 Apr 2005 01:08:54 +0000 http://www.alexking.org/blog/2005/04/20/porting-tasks-pro-to-adodb/#comment-4992 Yeah, I'm hoping to roll Postgres and Oracle in to the product i'm working on during the second round of development. Since you moved to PHP5 you may also want to check out the integrated SQLite database. Sorry for posting and trackbacking, I didn't think the comment went through so then I decided just to post on my blog. Yeah, I’m hoping to roll Postgres and Oracle in to the product i’m working on during the second round of development. Since you moved to PHP5 you may also want to check out the integrated SQLite database.

Sorry for posting and trackbacking, I didn’t think the comment went through so then I decided just to post on my blog.

]]> By: Ian Landsman's Weblog http://alexking.org/blog/2005/04/20/tasks-pro-on-adodb#comment-4991 Ian Landsman's Weblog Thu, 21 Apr 2005 00:58:51 +0000 http://www.alexking.org/blog/2005/04/20/porting-tasks-pro-to-adodb/#comment-4991 <strong>ADOdb</strong> Alex is porting Tasks to use ADOdb from straight MySQL. I've built HelpSpot from the ground up using it. I've been using it for several years and I'm really happy with it. He mentions the trouble Postgres can be if your moving from a MySQL/SQL Se... ADOdb

Alex is porting Tasks to use ADOdb from straight MySQL. I’ve built HelpSpot from the ground up using it. I’ve been using it for several years and I’m really happy with it.

He mentions the trouble Postgres can be if your moving from a MySQL/SQL Se…

]]> By: Alex http://alexking.org/blog/2005/04/20/tasks-pro-on-adodb#comment-4990 Alex Thu, 21 Apr 2005 00:21:08 +0000 http://www.alexking.org/blog/2005/04/20/porting-tasks-pro-to-adodb/#comment-4990 The majority of alternate database requests I get are for Postgres support. Also, with the uncertainty around the MySQL licensing stuff, I thought supporting another free database was a good hedge. The majority of alternate database requests I get are for Postgres support. Also, with the uncertainty around the MySQL licensing stuff, I thought supporting another free database was a good hedge.

]]> By: Ian Landsman http://alexking.org/blog/2005/04/20/tasks-pro-on-adodb#comment-4989 Ian Landsman Wed, 20 Apr 2005 23:59:36 +0000 http://www.alexking.org/blog/2005/04/20/porting-tasks-pro-to-adodb/#comment-4989 The ADOdb library is very good, I've used it for several years now. The <a href="http://www.userscape.com/products/helpspot/">help desk software</a> I'm working on is built with it from the ground up. Postgres is such a pain that I'm actually not going to support it, at least in v1. MySQL and M$ SQL Server use very similar dialects of SQL so supporting both of them is easy. It's also been my experience the you can get away with supporting MySQL OR Postgres and you're ok as most shops that use one are OK with the other as long as they don't have to buy an MS product. The ADOdb library is very good, I’ve used it for several years now. The help desk software I’m working on is built with it from the ground up. Postgres is such a pain that I’m actually not going to support it, at least in v1. MySQL and M$ SQL Server use very similar dialects of SQL so supporting both of them is easy.

It’s also been my experience the you can get away with supporting MySQL OR Postgres and you’re ok as most shops that use one are OK with the other as long as they don’t have to buy an MS product.

]]>