TC 2.0 and MySQL

[Oren Shemesh <or...@qwilt.com>]

I got confused by some different messages I have read here, so I would like
to ask:

Will TC 2.0 eventually support both MySQL and postgresql ?

Assuming the answer is 'yes':
  Is master branch currently expected to work with MySQL ?
Assuming the answer is 'no':
  I guess that docs/source/admin/traffic_ops_install.rst has to be updated,
because it contains the following text:

Note:: Although Traffic Ops supports both MySQL and Postgres as a database,
support for MySQL is more mature and better tested. It is best to use MySQL
when first getting started, and the rest of this guide assumes MySQL as the
database.

(I will be happy to update the doc, if indeed the answer is 'no')

-- 

*Oren Shemesh*
Qwilt | Work: +972-72-2221637| Mobile: +972-50-2281168 | orens@qwilt.com
<yo...@qwilt.com>

Re: TC 2.0 and MySQL

[Jeremy Mitchell <mi...@gmail.com>]

The last version of TC to support MySQL is 1.8. Anything after that is
Postgres only. Yes, if you find documentation errors please submit a jira (
https://issues.apache.org/jira/browse/TC) or a PR to
https://github.com/apache/incubator-trafficcontrol

Thanks!

On Tue, Jan 24, 2017 at 3:17 AM, Oren Shemesh <or...@qwilt.com> wrote:

> I got confused by some different messages I have read here, so I would like
> to ask:
>
> Will TC 2.0 eventually support both MySQL and postgresql ?
>
> Assuming the answer is 'yes':
>   Is master branch currently expected to work with MySQL ?
> Assuming the answer is 'no':
>   I guess that docs/source/admin/traffic_ops_install.rst has to be
> updated,
> because it contains the following text:
>
> Note:: Although Traffic Ops supports both MySQL and Postgres as a database,
> support for MySQL is more mature and better tested. It is best to use MySQL
> when first getting started, and the rest of this guide assumes MySQL as the
> database.
>
> (I will be happy to update the doc, if indeed the answer is 'no')
>
> --
>
> *Oren Shemesh*
> Qwilt | Work: +972-72-2221637| Mobile: +972-50-2281168 | orens@qwilt.com
> <yo...@qwilt.com>
>