Re: [Apiman-dev] APIMAN-451 DB Servers
Eric,
Perhaps you should start the request process now for access to those database servers.
I’m targeting MySQL Server 5.1.73 and Postgres 9.3 on this side. Exact server versions
probably not that important, just try and get close.
Databases: apiman_current, apiman_previous, apiman_empty
User: apiman
Password: apiman
Brandon
On Jun 18, 2015, at 5:40 AM, Brandon Gaisford <bgaisford(a)punagroup.com> wrote:
My sincere hope is that the change sets used to pre-populate the database with static
data is all developers will have to manage. So far so good, but the live DB requirement
was a surprise.
On Jun 18, 2015, at 3:06 AM, Eric Wittmann <eric.wittmann(a)redhat.com> wrote:
> Makes sense. I've long lamented that I didn't spend more time naming stuff
in the JPA layer. So I think this is a happy change.
>
> It's sad to learn that a live DB is needed to create the change sets. We do have
access to some live DB instances (of various types) here at RH - we can check them out and
use them for this purpose if necessary.
>
> The DB types we have available:
>
> DB2, sqlsrvr, mysql, oracle, postgres, sybase. And we have multiple versions of
each.
>
> If live DBs are required, then obviously creating changesets may continue to be a
largely manual process.
>
> -Eric
>
_______________________________________________
Apiman-dev mailing list
Apiman-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/apiman-dev