Re: basic use of migrations with MySQL...
On Jun 25, 2014, at 2:32 PM, Pascal Robert wrote: > And I had a similar problem this morning, after I found out that I needed to > add the ErAttributeExtension framework to get prototypes with JodaLocalTime > to work. > > No wonder we can't grow the community with such a tools mess... Amen, amen, amen. I say... Is there a swift path to get the EOModel into a corresponding "XML template", along with the appropriate plug-ins? Just asking, > > Envoyé de mon iPhone Baiss Eric Magnusson Cascade Web Design ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: basic use of migrations with MySQL...
And I had a similar problem this morning, after I found out that I needed to
add the ErAttributeExtension framework to get prototypes with JodaLocalTime to
work.
No wonder we can't grow the community with such a tools mess...
Envoyé de mon iPhone
> Le 2014-06-25 à 17:10, Timothy Worman a écrit :
>
>> On Jun 24, 2014, at 1:57 PM, Ray Kiddy wrote:
>>
>> On Tue, 24 Jun 2014 16:29:01 -0400
>> Theodore Petrosky wrote:
>>
>>> and you are using the MYSQL plugin from WO 5.4 as Pascal is
>>> suggesting?
>>
>>
>> Well, of course I had. Duh!
>>
>> And then ... I have just double-checked. I had put the framework into
>> the build path, but not high enough up to over-ride the non-working
>> functionality. Urf!
>
> This was my experience.
>
> I posted recently to the list that the Wonder OpenBase plugin had to be above
> the eoaccess framework in order to properly override the functionality in the
> built-in plugins. The migrations frameworks need to be able to call the
> proper synchronization framework and SQLHelper classes.
>
> Tim
> UCLA GSE&IS
>
>> Well, I am still going to add a document to the wocommunity site which
>> is just about Migrations.
>>
>> I bet the Wonder migrations code can check, if it is using a MySQL
>> plugin, that the class it is using is the correct version. At the very
>> least, this would make for a better error message. There should be a
>> way to stop people from stubbing their toe on this.
>>
>> - ray
>>
>>
>>>
On Jun 24, 2014, at 4:21 PM, Ray Kiddy wrote:
On Tue, 24 Jun 2014 16:17:51 -0400
Theodore Petrosky wrote:
> Ray,
>
> If I understand, (It always seems that I don’t understand the
> question), you want to alter a table through migrations. I have
> always done it like this.
>
>
> ERXMigrationTable theTable =
> database.existingTableNamed(“theTableIWantToAlter");
>
> theTable.existingColumnNamed(“theColumnName").setAllowsNull(false);
>
> Is this what you are looking for?
>
> Ted
This code:
ERXMigrationTable skuTable =
database.existingTableNamed("product_skus");
skuTable.newStringColumn("tag", 63, true);
Generates this SQL:
alter table skus null column tag varchar(63);
- ray
>> On Jun 24, 2014, at 3:59 PM, Ray Kiddy wrote:
>>
>>
>> I should have been using migrations for a long time, but I have
>> not. I have just never had the time to add another thing that
>> might break. But you know. But I thought I knew the theory of it.
>>
>> So, the only place I am seeing basic documentation on the
>> wocommunity site is in the page on creating an ERRest application.
>> Is this right? Did I miss something? I know there have been WOWODC
>> presentations, but that is not completely a replacement for a
>> simple how-to document.
>>
>> But starting out, migrations seemed pretty easy to use. Ok,
>> setting the encoding of the tables to latin1 instead of utf-8 was
>> not amazingly helpful, but I can deal.
>>
>> But then I tried my first table change, as opposed to a create.
>>
>> alter table foo_table null column1 column2 varchar(10);
>>
>> Hm. Not helpful. I guess falling back to reasonable defaults is
>> not what happens here. I tried adding things to my classpath,
>> such as the Wonder MySQL plugin framework. No difference.
>>
>> So, I now use my migration java sources as a convenient place for
>> the comments which give me the SQL I have to execute manually to
>> make this work. This is probably not the best use of this feature,
>> though.
>>
>> Any obvious things I am missing before I try to debug this and,
>> perhaps, put some basic documentation on the site?
>>
>> thanx - ray
>>
>>
>> ___
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/lists%40thetimmy.com
>>
>> This email sent to li...@thetimmy.com
>
>
> ___
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca
>
> This email sent to prob...@macti.ca
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
Re: basic use of migrations with MySQL...
On Jun 24, 2014, at 1:57 PM, Ray Kiddy wrote:
> On Tue, 24 Jun 2014 16:29:01 -0400
> Theodore Petrosky wrote:
>
>> and you are using the MYSQL plugin from WO 5.4 as Pascal is
>> suggesting?
>
>
> Well, of course I had. Duh!
>
> And then ... I have just double-checked. I had put the framework into
> the build path, but not high enough up to over-ride the non-working
> functionality. Urf!
This was my experience.
I posted recently to the list that the Wonder OpenBase plugin had to be above
the eoaccess framework in order to properly override the functionality in the
built-in plugins. The migrations frameworks need to be able to call the proper
synchronization framework and SQLHelper classes.
Tim
UCLA GSE&IS
> Well, I am still going to add a document to the wocommunity site which
> is just about Migrations.
>
> I bet the Wonder migrations code can check, if it is using a MySQL
> plugin, that the class it is using is the correct version. At the very
> least, this would make for a better error message. There should be a
> way to stop people from stubbing their toe on this.
>
> - ray
>
>
>>
>> On Jun 24, 2014, at 4:21 PM, Ray Kiddy wrote:
>>
>>> On Tue, 24 Jun 2014 16:17:51 -0400
>>> Theodore Petrosky wrote:
>>>
Ray,
If I understand, (It always seems that I don’t understand the
question), you want to alter a table through migrations. I have
always done it like this.
ERXMigrationTable theTable =
database.existingTableNamed(“theTableIWantToAlter");
theTable.existingColumnNamed(“theColumnName").setAllowsNull(false);
Is this what you are looking for?
Ted
>>>
>>> This code:
>>>
>>> ERXMigrationTable skuTable =
>>> database.existingTableNamed("product_skus");
>>> skuTable.newStringColumn("tag", 63, true);
>>>
>>> Generates this SQL:
>>>
>>> alter table skus null column tag varchar(63);
>>>
>>> - ray
>>>
On Jun 24, 2014, at 3:59 PM, Ray Kiddy wrote:
>
> I should have been using migrations for a long time, but I have
> not. I have just never had the time to add another thing that
> might break. But you know. But I thought I knew the theory of it.
>
> So, the only place I am seeing basic documentation on the
> wocommunity site is in the page on creating an ERRest application.
> Is this right? Did I miss something? I know there have been WOWODC
> presentations, but that is not completely a replacement for a
> simple how-to document.
>
> But starting out, migrations seemed pretty easy to use. Ok,
> setting the encoding of the tables to latin1 instead of utf-8 was
> not amazingly helpful, but I can deal.
>
> But then I tried my first table change, as opposed to a create.
>
> alter table foo_table null column1 column2 varchar(10);
>
> Hm. Not helpful. I guess falling back to reasonable defaults is
> not what happens here. I tried adding things to my classpath,
> such as the Wonder MySQL plugin framework. No difference.
>
> So, I now use my migration java sources as a convenient place for
> the comments which give me the SQL I have to execute manually to
> make this work. This is probably not the best use of this feature,
> though.
>
> Any obvious things I am missing before I try to debug this and,
> perhaps, put some basic documentation on the site?
>
> thanx - ray
>
>
> ___
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/lists%40thetimmy.com
>
> This email sent to li...@thetimmy.com
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
Re: basic use of migrations with MySQL...
On 25/06/2014, at 5:29 AM, Ray Kiddy wrote: > So, the only place I am seeing basic documentation on the wocommunity > site is in the page on creating an ERRest application. Is this right? > Did I miss something? I know there have been WOWODC presentations, but > that is not completely a replacement for a simple how-to document. There is some basic documentation on the package-level Javadoc page: http://jenkins.wocommunity.org/job/Wonder/lastSuccessfulBuild/javadoc/er/extensions/migration/package-summary.html It's minimal, but should get you going. -- Paul Hoadley http://logicsquad.net/ ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: basic use of migrations with MySQL...
On Tue, 24 Jun 2014 16:29:01 -0400
Theodore Petrosky wrote:
> and you are using the MYSQL plugin from WO 5.4 as Pascal is
> suggesting?
Well, of course I had. Duh!
And then ... I have just double-checked. I had put the framework into
the build path, but not high enough up to over-ride the non-working
functionality. Urf!
Well, I am still going to add a document to the wocommunity site which
is just about Migrations.
I bet the Wonder migrations code can check, if it is using a MySQL
plugin, that the class it is using is the correct version. At the very
least, this would make for a better error message. There should be a
way to stop people from stubbing their toe on this.
- ray
>
> On Jun 24, 2014, at 4:21 PM, Ray Kiddy wrote:
>
> > On Tue, 24 Jun 2014 16:17:51 -0400
> > Theodore Petrosky wrote:
> >
> >> Ray,
> >>
> >> If I understand, (It always seems that I don’t understand the
> >> question), you want to alter a table through migrations. I have
> >> always done it like this.
> >>
> >>
> >> ERXMigrationTable theTable =
> >> database.existingTableNamed(“theTableIWantToAlter");
> >>
> >> theTable.existingColumnNamed(“theColumnName").setAllowsNull(false);
> >>
> >> Is this what you are looking for?
> >>
> >> Ted
> >
> > This code:
> >
> > ERXMigrationTable skuTable =
> > database.existingTableNamed("product_skus");
> > skuTable.newStringColumn("tag", 63, true);
> >
> > Generates this SQL:
> >
> > alter table skus null column tag varchar(63);
> >
> > - ray
> >
> >> On Jun 24, 2014, at 3:59 PM, Ray Kiddy wrote:
> >>
> >>>
> >>> I should have been using migrations for a long time, but I have
> >>> not. I have just never had the time to add another thing that
> >>> might break. But you know. But I thought I knew the theory of it.
> >>>
> >>> So, the only place I am seeing basic documentation on the
> >>> wocommunity site is in the page on creating an ERRest application.
> >>> Is this right? Did I miss something? I know there have been WOWODC
> >>> presentations, but that is not completely a replacement for a
> >>> simple how-to document.
> >>>
> >>> But starting out, migrations seemed pretty easy to use. Ok,
> >>> setting the encoding of the tables to latin1 instead of utf-8 was
> >>> not amazingly helpful, but I can deal.
> >>>
> >>> But then I tried my first table change, as opposed to a create.
> >>>
> >>> alter table foo_table null column1 column2 varchar(10);
> >>>
> >>> Hm. Not helpful. I guess falling back to reasonable defaults is
> >>> not what happens here. I tried adding things to my classpath,
> >>> such as the Wonder MySQL plugin framework. No difference.
> >>>
> >>> So, I now use my migration java sources as a convenient place for
> >>> the comments which give me the SQL I have to execute manually to
> >>> make this work. This is probably not the best use of this feature,
> >>> though.
> >>>
> >>> Any obvious things I am missing before I try to debug this and,
> >>> perhaps, put some basic documentation on the site?
> >>>
> >>> thanx - ray
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
Re: basic use of migrations with MySQL...
On Tue, 24 Jun 2014 16:29:01 -0400
Theodore Petrosky wrote:
> and you are using the MYSQL plugin from WO 5.4 as Pascal is
> suggesting?
Well, of course I had. Duh!
And then ... I have just double-checked. I had put the framework into
the build path, but not high enough up to over-ride the non-working
functionality. Urf!
Well, I am still going to add a document to the wocommunity site which
is just about Migrations.
I bet the Wonder migrations code can check, if it is using a MySQL
plugin, that the class it is using is the correct version. At the very
least, this would make for a better error message. There should be a
way to stop people from stubbing their toe on this.
- ray
>
> On Jun 24, 2014, at 4:21 PM, Ray Kiddy wrote:
>
> > On Tue, 24 Jun 2014 16:17:51 -0400
> > Theodore Petrosky wrote:
> >
> >> Ray,
> >>
> >> If I understand, (It always seems that I don’t understand the
> >> question), you want to alter a table through migrations. I have
> >> always done it like this.
> >>
> >>
> >> ERXMigrationTable theTable =
> >> database.existingTableNamed(“theTableIWantToAlter");
> >>
> >> theTable.existingColumnNamed(“theColumnName").setAllowsNull(false);
> >>
> >> Is this what you are looking for?
> >>
> >> Ted
> >
> > This code:
> >
> > ERXMigrationTable skuTable =
> > database.existingTableNamed("product_skus");
> > skuTable.newStringColumn("tag", 63, true);
> >
> > Generates this SQL:
> >
> > alter table skus null column tag varchar(63);
> >
> > - ray
> >
> >> On Jun 24, 2014, at 3:59 PM, Ray Kiddy wrote:
> >>
> >>>
> >>> I should have been using migrations for a long time, but I have
> >>> not. I have just never had the time to add another thing that
> >>> might break. But you know. But I thought I knew the theory of it.
> >>>
> >>> So, the only place I am seeing basic documentation on the
> >>> wocommunity site is in the page on creating an ERRest application.
> >>> Is this right? Did I miss something? I know there have been WOWODC
> >>> presentations, but that is not completely a replacement for a
> >>> simple how-to document.
> >>>
> >>> But starting out, migrations seemed pretty easy to use. Ok,
> >>> setting the encoding of the tables to latin1 instead of utf-8 was
> >>> not amazingly helpful, but I can deal.
> >>>
> >>> But then I tried my first table change, as opposed to a create.
> >>>
> >>> alter table foo_table null column1 column2 varchar(10);
> >>>
> >>> Hm. Not helpful. I guess falling back to reasonable defaults is
> >>> not what happens here. I tried adding things to my classpath,
> >>> such as the Wonder MySQL plugin framework. No difference.
> >>>
> >>> So, I now use my migration java sources as a convenient place for
> >>> the comments which give me the SQL I have to execute manually to
> >>> make this work. This is probably not the best use of this feature,
> >>> though.
> >>>
> >>> Any obvious things I am missing before I try to debug this and,
> >>> perhaps, put some basic documentation on the site?
> >>>
> >>> thanx - ray
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
Re: basic use of migrations with MySQL...
On Tue, 24 Jun 2014 16:29:01 -0400
Theodore Petrosky wrote:
> and you are using the MYSQL plugin from WO 5.4 as Pascal is
> suggesting?
Well, of course I had. Duh!
And then ... I have just double-checked. I had put the framework into
the build path, but not high enough up to over-ride the non-working
functionality. Urf!
Well, I am still going to add a document to the wocommunity site which
is just about Migrations.
I bet the Wonder migrations code can check, if it is using a MySQL
plugin, that the class it is using is the correct version. At the very
least, this would make for a better error message. There should be a
way to stop people from stubbing their toe on this.
- ray
>
> On Jun 24, 2014, at 4:21 PM, Ray Kiddy wrote:
>
> > On Tue, 24 Jun 2014 16:17:51 -0400
> > Theodore Petrosky wrote:
> >
> >> Ray,
> >>
> >> If I understand, (It always seems that I don’t understand the
> >> question), you want to alter a table through migrations. I have
> >> always done it like this.
> >>
> >>
> >> ERXMigrationTable theTable =
> >> database.existingTableNamed(“theTableIWantToAlter");
> >>
> >> theTable.existingColumnNamed(“theColumnName").setAllowsNull(false);
> >>
> >> Is this what you are looking for?
> >>
> >> Ted
> >
> > This code:
> >
> > ERXMigrationTable skuTable =
> > database.existingTableNamed("product_skus");
> > skuTable.newStringColumn("tag", 63, true);
> >
> > Generates this SQL:
> >
> > alter table skus null column tag varchar(63);
> >
> > - ray
> >
> >> On Jun 24, 2014, at 3:59 PM, Ray Kiddy wrote:
> >>
> >>>
> >>> I should have been using migrations for a long time, but I have
> >>> not. I have just never had the time to add another thing that
> >>> might break. But you know. But I thought I knew the theory of it.
> >>>
> >>> So, the only place I am seeing basic documentation on the
> >>> wocommunity site is in the page on creating an ERRest application.
> >>> Is this right? Did I miss something? I know there have been WOWODC
> >>> presentations, but that is not completely a replacement for a
> >>> simple how-to document.
> >>>
> >>> But starting out, migrations seemed pretty easy to use. Ok,
> >>> setting the encoding of the tables to latin1 instead of utf-8 was
> >>> not amazingly helpful, but I can deal.
> >>>
> >>> But then I tried my first table change, as opposed to a create.
> >>>
> >>> alter table foo_table null column1 column2 varchar(10);
> >>>
> >>> Hm. Not helpful. I guess falling back to reasonable defaults is
> >>> not what happens here. I tried adding things to my classpath,
> >>> such as the Wonder MySQL plugin framework. No difference.
> >>>
> >>> So, I now use my migration java sources as a convenient place for
> >>> the comments which give me the SQL I have to execute manually to
> >>> make this work. This is probably not the best use of this feature,
> >>> though.
> >>>
> >>> Any obvious things I am missing before I try to debug this and,
> >>> perhaps, put some basic documentation on the site?
> >>>
> >>> thanx - ray
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
Re: basic use of migrations with MySQL...
and you are using the MYSQL plugin from WO 5.4 as Pascal is suggesting?
On Jun 24, 2014, at 4:21 PM, Ray Kiddy wrote:
> On Tue, 24 Jun 2014 16:17:51 -0400
> Theodore Petrosky wrote:
>
>> Ray,
>>
>> If I understand, (It always seems that I don’t understand the
>> question), you want to alter a table through migrations. I have
>> always done it like this.
>>
>>
>> ERXMigrationTable theTable =
>> database.existingTableNamed(“theTableIWantToAlter");
>>
>> theTable.existingColumnNamed(“theColumnName").setAllowsNull(false);
>>
>> Is this what you are looking for?
>>
>> Ted
>
> This code:
>
> ERXMigrationTable skuTable =
> database.existingTableNamed("product_skus");
> skuTable.newStringColumn("tag", 63, true);
>
> Generates this SQL:
>
> alter table skus null column tag varchar(63);
>
> - ray
>
>> On Jun 24, 2014, at 3:59 PM, Ray Kiddy wrote:
>>
>>>
>>> I should have been using migrations for a long time, but I have
>>> not. I have just never had the time to add another thing that might
>>> break. But you know. But I thought I knew the theory of it.
>>>
>>> So, the only place I am seeing basic documentation on the
>>> wocommunity site is in the page on creating an ERRest application.
>>> Is this right? Did I miss something? I know there have been WOWODC
>>> presentations, but that is not completely a replacement for a
>>> simple how-to document.
>>>
>>> But starting out, migrations seemed pretty easy to use. Ok, setting
>>> the encoding of the tables to latin1 instead of utf-8 was not
>>> amazingly helpful, but I can deal.
>>>
>>> But then I tried my first table change, as opposed to a create.
>>>
>>> alter table foo_table null column1 column2 varchar(10);
>>>
>>> Hm. Not helpful. I guess falling back to reasonable defaults is not
>>> what happens here. I tried adding things to my classpath, such as
>>> the Wonder MySQL plugin framework. No difference.
>>>
>>> So, I now use my migration java sources as a convenient place for
>>> the comments which give me the SQL I have to execute manually to
>>> make this work. This is probably not the best use of this feature,
>>> though.
>>>
>>> Any obvious things I am missing before I try to debug this and,
>>> perhaps, put some basic documentation on the site?
>>>
>>> thanx - ray
>
>
>
> ___
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com
>
> This email sent to tedp...@yahoo.com
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
Re: basic use of migrations with MySQL...
On Tue, 24 Jun 2014 16:17:51 -0400
Theodore Petrosky wrote:
> Ray,
>
> If I understand, (It always seems that I don’t understand the
> question), you want to alter a table through migrations. I have
> always done it like this.
>
>
> ERXMigrationTable theTable =
> database.existingTableNamed(“theTableIWantToAlter");
>
> theTable.existingColumnNamed(“theColumnName").setAllowsNull(false);
>
> Is this what you are looking for?
>
> Ted
This code:
ERXMigrationTable skuTable =
database.existingTableNamed("product_skus");
skuTable.newStringColumn("tag", 63, true);
Generates this SQL:
alter table skus null column tag varchar(63);
- ray
> On Jun 24, 2014, at 3:59 PM, Ray Kiddy wrote:
>
> >
> > I should have been using migrations for a long time, but I have
> > not. I have just never had the time to add another thing that might
> > break. But you know. But I thought I knew the theory of it.
> >
> > So, the only place I am seeing basic documentation on the
> > wocommunity site is in the page on creating an ERRest application.
> > Is this right? Did I miss something? I know there have been WOWODC
> > presentations, but that is not completely a replacement for a
> > simple how-to document.
> >
> > But starting out, migrations seemed pretty easy to use. Ok, setting
> > the encoding of the tables to latin1 instead of utf-8 was not
> > amazingly helpful, but I can deal.
> >
> > But then I tried my first table change, as opposed to a create.
> >
> >alter table foo_table null column1 column2 varchar(10);
> >
> > Hm. Not helpful. I guess falling back to reasonable defaults is not
> > what happens here. I tried adding things to my classpath, such as
> > the Wonder MySQL plugin framework. No difference.
> >
> > So, I now use my migration java sources as a convenient place for
> > the comments which give me the SQL I have to execute manually to
> > make this work. This is probably not the best use of this feature,
> > though.
> >
> > Any obvious things I am missing before I try to debug this and,
> > perhaps, put some basic documentation on the site?
> >
> > thanx - ray
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
Re: basic use of migrations with MySQL...
Ray, If I understand, (It always seems that I don’t understand the question), you want to alter a table through migrations. I have always done it like this. ERXMigrationTable theTable = database.existingTableNamed(“theTableIWantToAlter"); theTable.existingColumnNamed(“theColumnName").setAllowsNull(false); Is this what you are looking for? Ted On Jun 24, 2014, at 3:59 PM, Ray Kiddy wrote: > > I should have been using migrations for a long time, but I have not. I > have just never had the time to add another thing that might break. But > you know. But I thought I knew the theory of it. > > So, the only place I am seeing basic documentation on the wocommunity > site is in the page on creating an ERRest application. Is this right? > Did I miss something? I know there have been WOWODC presentations, but > that is not completely a replacement for a simple how-to document. > > But starting out, migrations seemed pretty easy to use. Ok, setting the > encoding of the tables to latin1 instead of utf-8 was not amazingly > helpful, but I can deal. > > But then I tried my first table change, as opposed to a create. > >alter table foo_table null column1 column2 varchar(10); > > Hm. Not helpful. I guess falling back to reasonable defaults is not > what happens here. I tried adding things to my classpath, such as the > Wonder MySQL plugin framework. No difference. > > So, I now use my migration java sources as a convenient place for the > comments which give me the SQL I have to execute manually to make this > work. This is probably not the best use of this feature, though. > > Any obvious things I am missing before I try to debug this and, > perhaps, put some basic documentation on the site? > > thanx - ray > ___ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com > > This email sent to tedp...@yahoo.com ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: basic use of migrations with MySQL...
Le 2014-06-24 à 15:59, Ray Kiddy a écrit : > > I should have been using migrations for a long time, but I have not. I > have just never had the time to add another thing that might break. But > you know. But I thought I knew the theory of it. > > So, the only place I am seeing basic documentation on the wocommunity > site is in the page on creating an ERRest application. Is this right? > Did I miss something? I know there have been WOWODC presentations, but > that is not completely a replacement for a simple how-to document. > > But starting out, migrations seemed pretty easy to use. Ok, setting the > encoding of the tables to latin1 instead of utf-8 was not amazingly > helpful, but I can deal. > > But then I tried my first table change, as opposed to a create. > >alter table foo_table null column1 column2 varchar(10); If I remember well, it happens if you use the MySQL plugin coming from WO 5.4. You have to use the one from Wonder. > Hm. Not helpful. I guess falling back to reasonable defaults is not > what happens here. I tried adding things to my classpath, such as the > Wonder MySQL plugin framework. No difference. > > So, I now use my migration java sources as a convenient place for the > comments which give me the SQL I have to execute manually to make this > work. This is probably not the best use of this feature, though. > > Any obvious things I am missing before I try to debug this and, > perhaps, put some basic documentation on the site? > > thanx - ray > ___ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca > > This email sent to prob...@macti.ca ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: basic use of migrations with MySQL...
Sorry, I missed the snippet of code you are using that has the problem. On Tue, Jun 24, 2014 at 2:59 PM, Ray Kiddy wrote: > > I should have been using migrations for a long time, but I have not. I > have just never had the time to add another thing that might break. But > you know. But I thought I knew the theory of it. > > So, the only place I am seeing basic documentation on the wocommunity > site is in the page on creating an ERRest application. Is this right? > Did I miss something? I know there have been WOWODC presentations, but > that is not completely a replacement for a simple how-to document. > > But starting out, migrations seemed pretty easy to use. Ok, setting the > encoding of the tables to latin1 instead of utf-8 was not amazingly > helpful, but I can deal. > > But then I tried my first table change, as opposed to a create. > > alter table foo_table null column1 column2 varchar(10); > > Hm. Not helpful. I guess falling back to reasonable defaults is not > what happens here. I tried adding things to my classpath, such as the > Wonder MySQL plugin framework. No difference. > > So, I now use my migration java sources as a convenient place for the > comments which give me the SQL I have to execute manually to make this > work. This is probably not the best use of this feature, though. > > Any obvious things I am missing before I try to debug this and, > perhaps, put some basic documentation on the site? > > thanx - ray > ___ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > > https://lists.apple.com/mailman/options/webobjects-dev/johnthuss%40gmail.com > > This email sent to johnth...@gmail.com ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
basic use of migrations with MySQL...
I should have been using migrations for a long time, but I have not. I have just never had the time to add another thing that might break. But you know. But I thought I knew the theory of it. So, the only place I am seeing basic documentation on the wocommunity site is in the page on creating an ERRest application. Is this right? Did I miss something? I know there have been WOWODC presentations, but that is not completely a replacement for a simple how-to document. But starting out, migrations seemed pretty easy to use. Ok, setting the encoding of the tables to latin1 instead of utf-8 was not amazingly helpful, but I can deal. But then I tried my first table change, as opposed to a create. alter table foo_table null column1 column2 varchar(10); Hm. Not helpful. I guess falling back to reasonable defaults is not what happens here. I tried adding things to my classpath, such as the Wonder MySQL plugin framework. No difference. So, I now use my migration java sources as a convenient place for the comments which give me the SQL I have to execute manually to make this work. This is probably not the best use of this feature, though. Any obvious things I am missing before I try to debug this and, perhaps, put some basic documentation on the site? thanx - ray ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
