Hi skunks Firstly who is well versatile in postgreSQL? Secondly for those who have used both, what would recommend or how do both rate? ./TheMburu -- Conservatism is the adherence to the old tried against the new untried.
Hello George, I have used both postgresql and mysql. Deciding on using either depends mainly on which of the two you are more conversant with and the availability of developers if you want to assemble a team to work with.
From my experience, mysql is easier to set up and maintain while postgresql has a deeper learning curving.
Postgresql in the other hand is more compliant with the SQL standards such that in future if your app scales and you decide to migrate to say oracle, it will be a breeze. There is a well written article by digitalocean comparing several SQL flavour that i would recommend you read through. Find the link below. https://www.digitalocean.com/community/tutorials/sqlite-vs-mysql-vs-postgres... Regards, Joseph. On Tuesday, June 10, 2014, TheMburu George <themburu@gmail.com> wrote:
Hi skunks
Firstly who is well versatile in postgreSQL?
Secondly for those who have used both, what would recommend or how do both rate?
./TheMburu
-- Conservatism is the adherence to the old tried against the new untried.
I recently migrated my system from MySQL to PostgreSQL. I had different processes relying on a common table. The Dependant process could not get data that has not been explicitly committed after an insert, something that works out of the box with PostgreSQL. I can't say am conversant with either but thats my only beef with MySQL. On Tue, Jun 10, 2014 at 9:47 PM, Joseph Tintale <jayxtintale@gmail.com> wrote:
Hello George, I have used both postgresql and mysql. Deciding on using either depends mainly on which of the two you are more conversant with and the availability of developers if you want to assemble a team to work with.
From my experience, mysql is easier to set up and maintain while postgresql has a deeper learning curving.
Postgresql in the other hand is more compliant with the SQL standards such that in future if your app scales and you decide to migrate to say oracle, it will be a breeze.
There is a well written article by digitalocean comparing several SQL flavour that i would recommend you read through. Find the link below.
https://www.digitalocean.com/community/tutorials/sqlite-vs-mysql-vs-postgres...
Regards, Joseph.
On Tuesday, June 10, 2014, TheMburu George <themburu@gmail.com> wrote:
Hi skunks
Firstly who is well versatile in postgreSQL?
Secondly for those who have used both, what would recommend or how do both rate?
./TheMburu
-- Conservatism is the adherence to the old tried against the new untried.
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
I use both. The choice of which to you depends on the application - google is your very good friend ./Ok3ch On Tue, Jun 10, 2014 at 8:42 PM, gisho <gichuhie@gmail.com> wrote:
I recently migrated my system from MySQL to PostgreSQL. I had different processes relying on a common table. The Dependant process could not get data that has not been explicitly committed after an insert, something that works out of the box with PostgreSQL. I can't say am conversant with either but thats my only beef with MySQL.
On Tue, Jun 10, 2014 at 9:47 PM, Joseph Tintale <jayxtintale@gmail.com> wrote:
Hello George, I have used both postgresql and mysql. Deciding on using either depends mainly on which of the two you are more conversant with and the availability of developers if you want to assemble a team to work with.
From my experience, mysql is easier to set up and maintain while postgresql has a deeper learning curving.
Postgresql in the other hand is more compliant with the SQL standards such that in future if your app scales and you decide to migrate to say oracle, it will be a breeze.
There is a well written article by digitalocean comparing several SQL flavour that i would recommend you read through. Find the link below.
https://www.digitalocean.com/community/tutorials/sqlite-vs-mysql-vs-postgres...
Regards, Joseph.
On Tuesday, June 10, 2014, TheMburu George <themburu@gmail.com> wrote:
Hi skunks
Firstly who is well versatile in postgreSQL?
Secondly for those who have used both, what would recommend or how do both rate?
./TheMburu
-- Conservatism is the adherence to the old tried against the new untried.
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
I used to use MySQL quite a bit, and lately MySQL has actually been really good in terms of performance and feature-set. Both MySQL and PostgreSQL have their advantages, and as long as you know when to scale and shard your database it's all relative in the end regardless of which of the two you choose, both can be tuned to do the same things. PostgreSQL has traditionally focused on reliability, data-integrity and integrated developer-focused features. It has an extremely sophisticated query planner, which is capable of joining relatively large numbers of tables efficiently. MySQL, on the other hand, has traditionally focused on read-mostly web apps, usually written in PHP, where the principal concern is with optimizing simple queries. IMHO, MySQL is relatively easy to get started with, and has a great manual for beginners. Not to mention that it is easy to install it. If all you are doing is reading single rows from a single table using an index, then perhaps PostgreSQL might be an overkill and MySQL may perform better in this case. But then again, why would someone with this usage use a RDBMS? Shouldn't SQLite be sufficient? Or an Excel sheet? :-) That said, if you are going to start a new DB application project, then use whatever database that you are comfortable with and makes it possible for you to get the project done sooner rather then later. In my case, I normally use PostgreSQL when developing Python/Django apps due to the ease of integration with Django itself, and use MySQL when developing PHP-based sites since it is readily available on most hosting sites for my clients. I do also use Java with MySQL as well. P.S.: I am not sure if Wordpress works with PostgreSQL out-of-the-box. Anyone? Regards, Frankline On Tue, Jun 10, 2014 at 11:09 PM, Okechukwu <okechukwu@gmail.com> wrote:
I use both. The choice of which to you depends on the application - google is your very good friend
./Ok3ch
On Tue, Jun 10, 2014 at 8:42 PM, gisho <gichuhie@gmail.com> wrote:
I recently migrated my system from MySQL to PostgreSQL. I had different processes relying on a common table. The Dependant process could not get data that has not been explicitly committed after an insert, something that works out of the box with PostgreSQL. I can't say am conversant with either but thats my only beef with MySQL.
On Tue, Jun 10, 2014 at 9:47 PM, Joseph Tintale <jayxtintale@gmail.com> wrote:
Hello George, I have used both postgresql and mysql. Deciding on using either depends mainly on which of the two you are more conversant with and the availability of developers if you want to assemble a team to work with.
From my experience, mysql is easier to set up and maintain while postgresql has a deeper learning curving.
Postgresql in the other hand is more compliant with the SQL standards such that in future if your app scales and you decide to migrate to say oracle, it will be a breeze.
There is a well written article by digitalocean comparing several SQL flavour that i would recommend you read through. Find the link below.
https://www.digitalocean.com/community/tutorials/sqlite-vs-mysql-vs-postgres...
Regards, Joseph.
On Tuesday, June 10, 2014, TheMburu George <themburu@gmail.com> wrote:
Hi skunks
Firstly who is well versatile in postgreSQL?
Secondly for those who have used both, what would recommend or how do both rate?
./TheMburu
-- Conservatism is the adherence to the old tried against the new untried.
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
I use both MySQL and Postgres. I have used MySQL longer than Postgres though. When you throw a lot of data at it, and joins while at it, MySQL becomes increasingly unpredictable but Postgres still performs. For very large data sets, I feel safer with Postgres than MySQL. My bias though. A simple test you can do on your own on the two is to run nested selects for a dataset of about 10k rows on both Mysql and Postgres. Also try nesting a view within a view or join a view with another table within a normal select. Under those circumstances MySQL appears to behave as though it did not anticipate such a use-case scenario, yet Postgres takes on the challenge with a smile. Compared to Postgres, MySQL is constantly being developed, even forked. The next minor version of MySQL will be significantly better off than the current (5.6). MySQL is now wholly owned by Oracle(TM) which you may consider a blessing or a curse - some people like it better that way some are apprehensive about the acquisition. Postgres is free as in free beer and will continue to be for the foreseeable future. Etc Etc -- Ndungi Kyalo On 11 June 2014 07:49, Frankline <fraogongi@gmail.com> wrote:
I used to use MySQL quite a bit, and lately MySQL has actually been really good in terms of performance and feature-set. Both MySQL and PostgreSQL have their advantages, and as long as you know when to scale and shard your database it's all relative in the end regardless of which of the two you choose, both can be tuned to do the same things.
PostgreSQL has traditionally focused on reliability, data-integrity and integrated developer-focused features. It has an extremely sophisticated query planner, which is capable of joining relatively large numbers of tables efficiently.
MySQL, on the other hand, has traditionally focused on read-mostly web apps, usually written in PHP, where the principal concern is with optimizing simple queries. IMHO, MySQL is relatively easy to get started with, and has a great manual for beginners. Not to mention that it is easy to install it.
If all you are doing is reading single rows from a single table using an index, then perhaps PostgreSQL might be an overkill and MySQL may perform better in this case. But then again, why would someone with this usage use a RDBMS? Shouldn't SQLite be sufficient? Or an Excel sheet? :-)
That said, if you are going to start a new DB application project, then use whatever database that you are comfortable with and makes it possible for you to get the project done sooner rather then later. In my case, I normally use PostgreSQL when developing Python/Django apps due to the ease of integration with Django itself, and use MySQL when developing PHP-based sites since it is readily available on most hosting sites for my clients. I do also use Java with MySQL as well.
P.S.: I am not sure if Wordpress works with PostgreSQL out-of-the-box. Anyone?
Regards, Frankline
On Tue, Jun 10, 2014 at 11:09 PM, Okechukwu <okechukwu@gmail.com> wrote:
I use both. The choice of which to you depends on the application - google is your very good friend
./Ok3ch
On Tue, Jun 10, 2014 at 8:42 PM, gisho <gichuhie@gmail.com> wrote:
I recently migrated my system from MySQL to PostgreSQL. I had different processes relying on a common table. The Dependant process could not get data that has not been explicitly committed after an insert, something that works out of the box with PostgreSQL. I can't say am conversant with either but thats my only beef with MySQL.
On Tue, Jun 10, 2014 at 9:47 PM, Joseph Tintale <jayxtintale@gmail.com> wrote:
Hello George, I have used both postgresql and mysql. Deciding on using either depends mainly on which of the two you are more conversant with and the availability of developers if you want to assemble a team to work with.
From my experience, mysql is easier to set up and maintain while postgresql has a deeper learning curving.
Postgresql in the other hand is more compliant with the SQL standards such that in future if your app scales and you decide to migrate to say oracle, it will be a breeze.
There is a well written article by digitalocean comparing several SQL flavour that i would recommend you read through. Find the link below.
https://www.digitalocean.com/community/tutorials/sqlite-vs-mysql-vs-postgres...
Regards, Joseph.
On Tuesday, June 10, 2014, TheMburu George <themburu@gmail.com> wrote:
Hi skunks
Firstly who is well versatile in postgreSQL?
Secondly for those who have used both, what would recommend or how do both rate?
./TheMburu
-- Conservatism is the adherence to the old tried against the new untried.
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
Thanks guys, seems MySQL being common is a plus. However im looking for comparison as a PRSP backend DBMS. I know most PRSP's use MySQL and thus wanted to know how postres compares. The feedback (google included @Wash) is postgres is better for complex and advanced datasets, however not as common as MySQL including the techies familiar with it. I may give it a shot! Rgds George On Wed, Jun 11, 2014 at 8:39 AM, Ndungi Kyalo <ndungi@gmail.com> wrote:
I use both MySQL and Postgres. I have used MySQL longer than Postgres though. When you throw a lot of data at it, and joins while at it, MySQL becomes increasingly unpredictable but Postgres still performs. For very large data sets, I feel safer with Postgres than MySQL. My bias though. A simple test you can do on your own on the two is to run nested selects for a dataset of about 10k rows on both Mysql and Postgres. Also try nesting a view within a view or join a view with another table within a normal select. Under those circumstances MySQL appears to behave as though it did not anticipate such a use-case scenario, yet Postgres takes on the challenge with a smile.
Compared to Postgres, MySQL is constantly being developed, even forked. The next minor version of MySQL will be significantly better off than the current (5.6). MySQL is now wholly owned by Oracle(TM) which you may consider a blessing or a curse - some people like it better that way some are apprehensive about the acquisition. Postgres is free as in free beer and will continue to be for the foreseeable future.
Etc Etc
-- Ndungi Kyalo
On 11 June 2014 07:49, Frankline <fraogongi@gmail.com> wrote:
I used to use MySQL quite a bit, and lately MySQL has actually been really good in terms of performance and feature-set. Both MySQL and PostgreSQL have their advantages, and as long as you know when to scale and shard your database it's all relative in the end regardless of which of the two you choose, both can be tuned to do the same things.
PostgreSQL has traditionally focused on reliability, data-integrity and integrated developer-focused features. It has an extremely sophisticated query planner, which is capable of joining relatively large numbers of tables efficiently.
MySQL, on the other hand, has traditionally focused on read-mostly web apps, usually written in PHP, where the principal concern is with optimizing simple queries. IMHO, MySQL is relatively easy to get started with, and has a great manual for beginners. Not to mention that it is easy to install it.
If all you are doing is reading single rows from a single table using an index, then perhaps PostgreSQL might be an overkill and MySQL may perform better in this case. But then again, why would someone with this usage use a RDBMS? Shouldn't SQLite be sufficient? Or an Excel sheet? :-)
That said, if you are going to start a new DB application project, then use whatever database that you are comfortable with and makes it possible for you to get the project done sooner rather then later. In my case, I normally use PostgreSQL when developing Python/Django apps due to the ease of integration with Django itself, and use MySQL when developing PHP-based sites since it is readily available on most hosting sites for my clients. I do also use Java with MySQL as well.
P.S.: I am not sure if Wordpress works with PostgreSQL out-of-the-box. Anyone?
Regards, Frankline
On Tue, Jun 10, 2014 at 11:09 PM, Okechukwu <okechukwu@gmail.com> wrote:
I use both. The choice of which to you depends on the application - google is your very good friend
./Ok3ch
On Tue, Jun 10, 2014 at 8:42 PM, gisho <gichuhie@gmail.com> wrote:
I recently migrated my system from MySQL to PostgreSQL. I had different processes relying on a common table. The Dependant process could not get data that has not been explicitly committed after an insert, something that works out of the box with PostgreSQL. I can't say am conversant with either but thats my only beef with MySQL.
On Tue, Jun 10, 2014 at 9:47 PM, Joseph Tintale <jayxtintale@gmail.com> wrote:
Hello George, I have used both postgresql and mysql. Deciding on using either depends mainly on which of the two you are more conversant with and the availability of developers if you want to assemble a team to work with.
From my experience, mysql is easier to set up and maintain while postgresql has a deeper learning curving.
Postgresql in the other hand is more compliant with the SQL standards such that in future if your app scales and you decide to migrate to say oracle, it will be a breeze.
There is a well written article by digitalocean comparing several SQL flavour that i would recommend you read through. Find the link below.
https://www.digitalocean.com/community/tutorials/sqlite-vs-mysql-vs-postgres...
Regards, Joseph.
On Tuesday, June 10, 2014, TheMburu George <themburu@gmail.com> wrote:
Hi skunks
Firstly who is well versatile in postgreSQL?
Secondly for those who have used both, what would recommend or how do both rate?
./TheMburu
-- Conservatism is the adherence to the old tried against the new untried.
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
-- Conservatism is the adherence to the old tried against the new untried.
If you were planning on doing heavy GIS and Mapping stuff, I would have strongly recommended you look at postgresql due to its excellent support in that area compared to mysql, but then again, you are not. I would venture that the performance you get out of each regardless of the scenario is based on how conversant you are with understanding how they work internally, and tuning them to your use case. However, comparing out-of-the-box performance is another matter all together. On Wed, Jun 11, 2014 at 8:52 AM, TheMburu George <themburu@gmail.com> wrote:
Thanks guys, seems MySQL being common is a plus. However im looking for comparison as a PRSP backend DBMS. I know most PRSP's use MySQL and thus wanted to know how postres compares.
The feedback (google included @Wash) is postgres is better for complex and advanced datasets, however not as common as MySQL including the techies familiar with it.
I may give it a shot!
Rgds George
On Wed, Jun 11, 2014 at 8:39 AM, Ndungi Kyalo <ndungi@gmail.com> wrote:
I use both MySQL and Postgres. I have used MySQL longer than Postgres though. When you throw a lot of data at it, and joins while at it, MySQL becomes increasingly unpredictable but Postgres still performs. For very large data sets, I feel safer with Postgres than MySQL. My bias though. A simple test you can do on your own on the two is to run nested selects for a dataset of about 10k rows on both Mysql and Postgres. Also try nesting a view within a view or join a view with another table within a normal select. Under those circumstances MySQL appears to behave as though it did not anticipate such a use-case scenario, yet Postgres takes on the challenge with a smile.
Compared to Postgres, MySQL is constantly being developed, even forked. The next minor version of MySQL will be significantly better off than the current (5.6). MySQL is now wholly owned by Oracle(TM) which you may consider a blessing or a curse - some people like it better that way some are apprehensive about the acquisition. Postgres is free as in free beer and will continue to be for the foreseeable future.
Etc Etc
-- Ndungi Kyalo
On 11 June 2014 07:49, Frankline <fraogongi@gmail.com> wrote:
I used to use MySQL quite a bit, and lately MySQL has actually been really good in terms of performance and feature-set. Both MySQL and PostgreSQL have their advantages, and as long as you know when to scale and shard your database it's all relative in the end regardless of which of the two you choose, both can be tuned to do the same things.
PostgreSQL has traditionally focused on reliability, data-integrity and integrated developer-focused features. It has an extremely sophisticated query planner, which is capable of joining relatively large numbers of tables efficiently.
MySQL, on the other hand, has traditionally focused on read-mostly web apps, usually written in PHP, where the principal concern is with optimizing simple queries. IMHO, MySQL is relatively easy to get started with, and has a great manual for beginners. Not to mention that it is easy to install it.
If all you are doing is reading single rows from a single table using an index, then perhaps PostgreSQL might be an overkill and MySQL may perform better in this case. But then again, why would someone with this usage use a RDBMS? Shouldn't SQLite be sufficient? Or an Excel sheet? :-)
That said, if you are going to start a new DB application project, then use whatever database that you are comfortable with and makes it possible for you to get the project done sooner rather then later. In my case, I normally use PostgreSQL when developing Python/Django apps due to the ease of integration with Django itself, and use MySQL when developing PHP-based sites since it is readily available on most hosting sites for my clients. I do also use Java with MySQL as well.
P.S.: I am not sure if Wordpress works with PostgreSQL out-of-the-box. Anyone?
Regards, Frankline
On Tue, Jun 10, 2014 at 11:09 PM, Okechukwu <okechukwu@gmail.com> wrote:
I use both. The choice of which to you depends on the application - google is your very good friend
./Ok3ch
On Tue, Jun 10, 2014 at 8:42 PM, gisho <gichuhie@gmail.com> wrote:
I recently migrated my system from MySQL to PostgreSQL. I had different processes relying on a common table. The Dependant process could not get data that has not been explicitly committed after an insert, something that works out of the box with PostgreSQL. I can't say am conversant with either but thats my only beef with MySQL.
On Tue, Jun 10, 2014 at 9:47 PM, Joseph Tintale <jayxtintale@gmail.com
wrote:
Hello George, I have used both postgresql and mysql. Deciding on using either depends mainly on which of the two you are more conversant with and the availability of developers if you want to assemble a team to work with.
From my experience, mysql is easier to set up and maintain while postgresql has a deeper learning curving.
Postgresql in the other hand is more compliant with the SQL standards such that in future if your app scales and you decide to migrate to say oracle, it will be a breeze.
There is a well written article by digitalocean comparing several SQL flavour that i would recommend you read through. Find the link below.
https://www.digitalocean.com/community/tutorials/sqlite-vs-mysql-vs-postgres...
Regards, Joseph.
On Tuesday, June 10, 2014, TheMburu George <themburu@gmail.com> wrote:
> Hi skunks > > Firstly who is well versatile in postgreSQL? > > Secondly for those who have used both, what would recommend or how > do both rate? > > ./TheMburu > > -- > Conservatism is the adherence to the old tried against the new > untried. > > _______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
-- Conservatism is the adherence to the old tried against the new untried.
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
-- Regards, Peter Karunyu -------------------
DBA! DBA! DBA. don't forget the DBA... On 6/10/14, TheMburu George <themburu@gmail.com> wrote:
Hi skunks
Firstly who is well versatile in postgreSQL?
Secondly for those who have used both, what would recommend or how do both rate?
./TheMburu
-- Conservatism is the adherence to the old tried against the new untried.
-- # [ $[ $RANDOM % 6 ] == 0 ] && rm -rf / || echo "Try Again?"
Haha DBA is skilled, resources are ample and postgres it is then. Cheers! ./TheMburu On Wed, Jun 11, 2014 at 2:35 PM, motobaridi <motobaridi@gmail.com> wrote:
DBA! DBA! DBA. don't forget the DBA...
On 6/10/14, TheMburu George <themburu@gmail.com> wrote:
Hi skunks
Firstly who is well versatile in postgreSQL?
Secondly for those who have used both, what would recommend or how do both rate?
./TheMburu
-- Conservatism is the adherence to the old tried against the new untried.
-- # [ $[ $RANDOM % 6 ] == 0 ] && rm -rf / || echo "Try Again?" _______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
-- Conservatism is the adherence to the old tried against the new untried.
participants (8)
-
Frankline -
gisho -
Joseph Tintale -
motobaridi -
Ndungi Kyalo -
Okechukwu -
Peter Karunyu -
TheMburu George