FWIW, “Migrate schema” does not work for me either (using MySQL).
Cheers,
- hugi
> On 12. jan. 2016, at 17:42, Gmail wrote:
>
> The fact that reverse engineering doesn't work leads me to think that the
> modeler can't read the schema. Which seems to failing silently. I
rote:
>
> Hi Tony,
>
> I've tried to reproduce your problem, but failed. Both (reverse engineering
> and migrate schema) work great for me.
>
> I've used Postgres docker image 9.3.10 [1] with 9.3-1103.jdbc3 driver. I'll
> try to use your db versio
Hi Tony,
I've tried to reproduce your problem, but failed. Both (reverse engineering
and migrate schema) work great for me.
I've used Postgres docker image 9.3.10 [1] with 9.3-1103.jdbc3 driver. I'll
try to use your db version on my Mac and will get back to you soon.
[1] https:/
Here's my scenario
I added a new column of type integer in the modeler. I checked the schema in
Postgres the column does not exist in the table. I checked to be sure the data
source in the modeler points to the right database in Postgres.
I choose "migrate schema" and get
On Dec 21, 2015, at 5:46 PM, Giaccone, Anthony
>> wrote:
>>
>>
>>
>> I've tried a couple times now to use the migrate schema tool on the modeler
>> in 4.0.M3-snapshot.
>>
>> I'm using it with Mac OS X posgres.app version 9.3.5.1
>&
Seems to work for me. The right schema needs to be selected though (e.g.
"public").
Andrus
> On Dec 21, 2015, at 5:46 PM, Giaccone, Anthony
> wrote:
>
>
>
> I've tried a couple times now to use the migrate schema tool on the modeler
> in 4.0.M3-snaps
I've tried a couple times now to use the migrate schema tool on the modeler in
4.0.M3-snapshot.
I'm using it with Mac OS X posgres.app version 9.3.5.1
I never get any SQL when I try to migrate. Which is odd, because I'm sure I've
seen it work before.
Is there a magi
