I'm pleased to announce that we released DataMapper 1.0 "Vermouth"
earlier today.
Thank you to everyone in the community, especially this mailing list
and the IRC channel. There's no way we could've reached this milestone
without your encouragement and assistance.
It's extremely rewarding to see DM hit 1.0, but at the same time it
also sets a baseline for future development to build on. In some ways
we're only just getting started, the future we have planned for DM is
even more ambitious. I'll be writing more about our plans in the
coming weeks.
Before you install
------------------
The installation process for DM 1.0 is pretty similar to what it was
previously in 0.10.x and 0.9.x with a few exceptions:
1) Using auto-migration and auto-upgrading require dm-migrations
rather than just dm-core. The reason for this is that dm-migrations
should share a lot of code with auto-migrations, but they don’t, and
in an attempt to DRY things up we’ve centralized all the code in one
package and will begin refactoring the code over the coming months.
2) Transactions require the use of the dm-transactions gem.
3) It is no longer necessary to gem install data_objects or any do_*
gem directly. Each DO based adapter has been extracted into their own
gems, and installing them will setup the dependencies on dm-core and
the appropriate DO gem(s). The new adapters are:
In previous release announcements I've provided details about the
changes, so I'm not going to repeat myself ;) Instead I'm going to
refer you to the list of 61 tickets we've resolved for the 1.0
milestone:
> I'm pleased to announce that we released DataMapper 1.0 "Vermouth" > earlier today.
> Thank you to everyone in the community, especially this mailing list > and the IRC channel. There's no way we could've reached this milestone > without your encouragement and assistance.
> It's extremely rewarding to see DM hit 1.0, but at the same time it > also sets a baseline for future development to build on. In some ways > we're only just getting started, the future we have planned for DM is > even more ambitious. I'll be writing more about our plans in the > coming weeks.
> Before you install > ------------------
> The installation process for DM 1.0 is pretty similar to what it was > previously in 0.10.x and 0.9.x with a few exceptions:
> 1) Using auto-migration and auto-upgrading require dm-migrations > rather than just dm-core. The reason for this is that dm-migrations > should share a lot of code with auto-migrations, but they don’t, and > in an attempt to DRY things up we’ve centralized all the code in one > package and will begin refactoring the code over the coming months.
> 2) Transactions require the use of the dm-transactions gem.
> 3) It is no longer necessary to gem install data_objects or any do_* > gem directly. Each DO based adapter has been extracted into their own > gems, and installing them will setup the dependencies on dm-core and > the appropriate DO gem(s). The new adapters are:
> In previous release announcements I've provided details about the > changes, so I'm not going to repeat myself ;) Instead I'm going to > refer you to the list of 61 tickets we've resolved for the 1.0 > milestone:
> -- > You received this message because you are subscribed to the Google Groups > "DataMapper" group. > To post to this group, send email to datamapper@googlegroups.com. > To unsubscribe from this group, send email to > datamapper+unsubscribe@googlegroups.com<datamapper%2Bunsubscribe@googlegrou ps.com> > . > For more options, visit this group at > http://groups.google.com/group/datamapper?hl=en.
> On 9 June 2010 10:04, Dan Kubb (dkubb) <dan.k...@gmail.com> wrote:
> > I'm pleased to announce that we released DataMapper 1.0 "Vermouth"
> > earlier today.
> > Thank you to everyone in the community, especially this mailing list
> > and the IRC channel. There's no way we could've reached this milestone
> > without your encouragement and assistance.
> > It's extremely rewarding to see DM hit 1.0, but at the same time it
> > also sets a baseline for future development to build on. In some ways
> > we're only just getting started, the future we have planned for DM is
> > even more ambitious. I'll be writing more about our plans in the
> > coming weeks.
> > Before you install
> > ------------------
> > The installation process for DM 1.0 is pretty similar to what it was
> > previously in 0.10.x and 0.9.x with a few exceptions:
> > 1) Using auto-migration and auto-upgrading require dm-migrations
> > rather than just dm-core. The reason for this is that dm-migrations
> > should share a lot of code with auto-migrations, but they don’t, and
> > in an attempt to DRY things up we’ve centralized all the code in one
> > package and will begin refactoring the code over the coming months.
> > 2) Transactions require the use of the dm-transactions gem.
> > 3) It is no longer necessary to gem install data_objects or any do_*
> > gem directly. Each DO based adapter has been extracted into their own
> > gems, and installing them will setup the dependencies on dm-core and
> > the appropriate DO gem(s). The new adapters are:
> > In previous release announcements I've provided details about the
> > changes, so I'm not going to repeat myself ;) Instead I'm going to
> > refer you to the list of 61 tickets we've resolved for the 1.0
> > milestone:
> > --
> > You received this message because you are subscribed to the Google Groups
> > "DataMapper" group.
> > To post to this group, send email to datamapper@googlegroups.com.
> > To unsubscribe from this group, send email to
> > datamapper+unsubscribe@googlegroups.com<datamapper%2Bunsubscribe@googlegrou ps.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/datamapper?hl=en.
> Thanks *so much* to everyone involved! Thx for every discussion, > ticket, patch, .. Seriously, I mean it!
> Now on to making DataMapper even more awesome!
> cheers > snusnu
> On Jun 9, 2:07 am, Daniel N <has....@gmail.com> wrote: >> So very very awesome. :)
>> Congratulations guys, this is really cool.
>> On 9 June 2010 10:04, Dan Kubb (dkubb) <dan.k...@gmail.com> wrote:
>>> I'm pleased to announce that we released DataMapper 1.0 "Vermouth" >>> earlier today.
>>> Thank you to everyone in the community, especially this mailing list >>> and the IRC channel. There's no way we could've reached this milestone >>> without your encouragement and assistance.
>>> It's extremely rewarding to see DM hit 1.0, but at the same time it >>> also sets a baseline for future development to build on. In some ways >>> we're only just getting started, the future we have planned for DM is >>> even more ambitious. I'll be writing more about our plans in the >>> coming weeks.
>>> Before you install >>> ------------------
>>> The installation process for DM 1.0 is pretty similar to what it was >>> previously in 0.10.x and 0.9.x with a few exceptions:
>>> 1) Using auto-migration and auto-upgrading require dm-migrations >>> rather than just dm-core. The reason for this is that dm-migrations >>> should share a lot of code with auto-migrations, but they don’t, and >>> in an attempt to DRY things up we’ve centralized all the code in one >>> package and will begin refactoring the code over the coming months.
>>> 2) Transactions require the use of the dm-transactions gem.
>>> 3) It is no longer necessary to gem install data_objects or any do_* >>> gem directly. Each DO based adapter has been extracted into their own >>> gems, and installing them will setup the dependencies on dm-core and >>> the appropriate DO gem(s). The new adapters are:
>>> In previous release announcements I've provided details about the >>> changes, so I'm not going to repeat myself ;) Instead I'm going to >>> refer you to the list of 61 tickets we've resolved for the 1.0 >>> milestone:
>>> -- >>> You received this message because you are subscribed to the Google Groups >>> "DataMapper" group. >>> To post to this group, send email to datamapper@googlegroups.com. >>> To unsubscribe from this group, send email to >>> datamapper+unsubscribe@googlegroups.com<datamapper%2Bunsubscribe@googlegrou ps.com> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/datamapper?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "DataMapper" group. > To post to this group, send email to datamapper@googlegroups.com. > To unsubscribe from this group, send email to datamapper+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/datamapper?hl=en.
Now, after installing this version, I'm getting the following error
when using a mysql database:
- /var/lib/gems/1.9.0/gems/do_mysql-0.10.2/lib/do_mysql/
do_mysql.so: undefined symbol: rb_default_internal_encoding
can you please give some help, thanks
On Jun 9, 4:47 am, Roy Wright <r...@wright.org> wrote:
> On Jun 8, 2010, at 7:23 PM, Martin Gamsjaeger wrote:
> > Yes! finally! a dream came true :P
> > Thanks *so much* to everyone involved! Thx for every discussion,
> > ticket, patch, .. Seriously, I mean it!
> > Now on to making DataMapper even more awesome!
> > cheers
> > snusnu
> > On Jun 9, 2:07 am, Daniel N <has....@gmail.com> wrote:
> >> So very very awesome. :)
> >> Congratulations guys, this is really cool.
> >> On 9 June 2010 10:04, Dan Kubb (dkubb) <dan.k...@gmail.com> wrote:
> >>> I'm pleased to announce that we released DataMapper 1.0 "Vermouth"
> >>> earlier today.
> >>> Thank you to everyone in the community, especially this mailing list
> >>> and the IRC channel. There's no way we could've reached this milestone
> >>> without your encouragement and assistance.
> >>> It's extremely rewarding to see DM hit 1.0, but at the same time it
> >>> also sets a baseline for future development to build on. In some ways
> >>> we're only just getting started, the future we have planned for DM is
> >>> even more ambitious. I'll be writing more about our plans in the
> >>> coming weeks.
> >>> Before you install
> >>> ------------------
> >>> The installation process for DM 1.0 is pretty similar to what it was
> >>> previously in 0.10.x and 0.9.x with a few exceptions:
> >>> 1) Using auto-migration and auto-upgrading require dm-migrations
> >>> rather than just dm-core. The reason for this is that dm-migrations
> >>> should share a lot of code with auto-migrations, but they don’t, and
> >>> in an attempt to DRY things up we’ve centralized all the code in one
> >>> package and will begin refactoring the code over the coming months.
> >>> 2) Transactions require the use of the dm-transactions gem.
> >>> 3) It is no longer necessary to gem install data_objects or any do_*
> >>> gem directly. Each DO based adapter has been extracted into their own
> >>> gems, and installing them will setup the dependencies on dm-core and
> >>> the appropriate DO gem(s). The new adapters are:
> >>> The next thing you want to do is decide which adapter you want to use.
> >>> For example if you want to use sqlite, do:
> >>> $ gem install dm-sqlite-adapter
> >>> This should pull in data_objects and do_sqlite3 automatically, so no
> >>> need to specify either of those explicitly anymore.
> >>> It’s likely you’ll want to use migrations (for classic or auto-
> >>> migrations), and transactions when using sqlite, so to install them
> >>> do:
> >>> $ gem install dm-migrations dm-transactions
> >>> There is also a metagem which combines several gems into a single
> >>> package:
> >>> $ gem install data_mapper
> >>> This pulls a nice base stack for DM development. The gems included
> >>> are:
> >>> In previous release announcements I've provided details about the
> >>> changes, so I'm not going to repeat myself ;) Instead I'm going to
> >>> refer you to the list of 61 tickets we've resolved for the 1.0
> >>> milestone:
> >>> --
> >>> You received this message because you are subscribed to the Google Groups
> >>> "DataMapper" group.
> >>> To post to this group, send email to datamapper@googlegroups.com.
> >>> To unsubscribe from this group, send email to
> >>> datamapper+unsubscribe@googlegroups.com<datamapper%2Bunsubscribe@googlegrou ps.com>
> >>> .
> >>> For more options, visit this group at
> >>>http://groups.google.com/group/datamapper?hl=en.
> > --
> > You received this message because you are subscribed to the Google Groups "DataMapper" group.
> > To post to this group, send email to datamapper@googlegroups.com.
> > To unsubscribe from this group, send email to datamapper+unsubscribe@googlegroups.com.
> > For more options, visit this group athttp://groups.google.com/group/datamapper?hl=en.
On 9 Jun., 12:25, whity <andregoncalo.b...@gmail.com> wrote:
> Now, after installing this version, I'm getting the following error
> when using a mysql database:
> - /var/lib/gems/1.9.0/gems/do_mysql-0.10.2/lib/do_mysql/
> do_mysql.so: undefined symbol: rb_default_internal_encoding
Sounds like it would work with ruby 1.9 ;-) And that someone didn't
consider
1.8 for their development. Encoding.default_internal is something ruby
1.9.
File a Bug.
On Wed, Jun 09, 2010 at 03:25:00AM -0700, whity wrote: > hi there,
> First of all, Congratulations!
> Now, after installing this version, I'm getting the following error > when using a mysql database: > - /var/lib/gems/1.9.0/gems/do_mysql-0.10.2/lib/do_mysql/ > do_mysql.so: undefined symbol: rb_default_internal_encoding
> can you please give some help, thanks
> On Jun 9, 4:47 am, Roy Wright <r...@wright.org> wrote: > > Whoooooop!
> > Congratulations!
> > And a great big THANK YOU!
> > On Jun 8, 2010, at 7:23 PM, Martin Gamsjaeger wrote:
> > > Yes! finally! a dream came true :P
> > > Thanks *so much* to everyone involved! Thx for every discussion, > > > ticket, patch, .. Seriously, I mean it!
> > > Now on to making DataMapper even more awesome!
> > > cheers > > > snusnu
> > > On Jun 9, 2:07 am, Daniel N <has....@gmail.com> wrote: > > >> So very very awesome. :)
> > >> Congratulations guys, this is really cool.
> > >> On 9 June 2010 10:04, Dan Kubb (dkubb) <dan.k...@gmail.com> wrote:
> > >>> I'm pleased to announce that we released DataMapper 1.0 "Vermouth" > > >>> earlier today.
> > >>> Thank you to everyone in the community, especially this mailing list > > >>> and the IRC channel. There's no way we could've reached this milestone > > >>> without your encouragement and assistance.
> > >>> It's extremely rewarding to see DM hit 1.0, but at the same time it > > >>> also sets a baseline for future development to build on. In some ways > > >>> we're only just getting started, the future we have planned for DM is > > >>> even more ambitious. I'll be writing more about our plans in the > > >>> coming weeks.
> > >>> Before you install > > >>> ------------------
> > >>> The installation process for DM 1.0 is pretty similar to what it was > > >>> previously in 0.10.x and 0.9.x with a few exceptions:
> > >>> 1) Using auto-migration and auto-upgrading require dm-migrations > > >>> rather than just dm-core. The reason for this is that dm-migrations > > >>> should share a lot of code with auto-migrations, but they don’t, and > > >>> in an attempt to DRY things up we’ve centralized all the code in one > > >>> package and will begin refactoring the code over the coming months.
> > >>> 2) Transactions require the use of the dm-transactions gem.
> > >>> 3) It is no longer necessary to gem install data_objects or any do_* > > >>> gem directly. Each DO based adapter has been extracted into their own > > >>> gems, and installing them will setup the dependencies on dm-core and > > >>> the appropriate DO gem(s). The new adapters are:
> > >>> The next thing you want to do is decide which adapter you want to use. > > >>> For example if you want to use sqlite, do:
> > >>> $ gem install dm-sqlite-adapter
> > >>> This should pull in data_objects and do_sqlite3 automatically, so no > > >>> need to specify either of those explicitly anymore.
> > >>> It’s likely you’ll want to use migrations (for classic or auto- > > >>> migrations), and transactions when using sqlite, so to install them > > >>> do:
> > >>> In previous release announcements I've provided details about the > > >>> changes, so I'm not going to repeat myself ;) Instead I'm going to > > >>> refer you to the list of 61 tickets we've resolved for the 1.0 > > >>> milestone:
> > >>> -- > > >>> You received this message because you are subscribed to the Google Groups > > >>> "DataMapper" group. > > >>> To post to this group, send email to datamapper@googlegroups.com. > > >>> To unsubscribe from this group, send email to > > >>> datamapper+unsubscribe@googlegroups.com<datamapper%2Bunsubscribe@googlegrou ps.com> > > >>> . > > >>> For more options, visit this group at > > >>>http://groups.google.com/group/datamapper?hl=en.
> > > -- > > > You received this message because you are subscribed to the Google Groups "DataMapper" group. > > > To post to this group, send email to datamapper@googlegroups.com. > > > To unsubscribe from this group, send email to datamapper+unsubscribe@googlegroups.com. > > > For more options, visit this group athttp://groups.google.com/group/datamapper?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "DataMapper" group. > To post to this group, send email to datamapper@googlegroups.com. > To unsubscribe from this group, send email to datamapper+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/datamapper?hl=en.
> Sounds like it would work with ruby 1.9 ;-) And that someone didn't
> consider 1.8 for their development. Encoding.default_internal is
> something ruby 1.9. File a Bug.
Stupid idea of mine. Ignore that. And why are you using 1.9.0 and not
1.9.1 btw? And yep, it's not do_* anymore (well it is, but don't
require
that directly), instead use dm-adapter-mysql (reading release notes
helps). And that do seems a bit old.
> Are you sure the version of your do_mysql gem (0.10.2) is korrekt in
> this place?
> BTW: Congratulations to the dm-core team, you spend a lot of time and
> effort making DataMapper my ruby orm of choice!
> On Wed, Jun 09, 2010 at 03:25:00AM -0700, whity wrote:
> > hi there,
> > First of all, Congratulations!
> > Now, after installing this version, I'm getting the following error
> > when using a mysql database:
> > - /var/lib/gems/1.9.0/gems/do_mysql-0.10.2/lib/do_mysql/
> > do_mysql.so: undefined symbol: rb_default_internal_encoding
> > can you please give some help, thanks
> > On Jun 9, 4:47 am, Roy Wright <r...@wright.org> wrote:
> > > Whoooooop!
> > > Congratulations!
> > > And a great big THANK YOU!
> > > On Jun 8, 2010, at 7:23 PM, Martin Gamsjaeger wrote:
> > > > Yes! finally! a dream came true :P
> > > > Thanks *so much* to everyone involved! Thx for every discussion,
> > > > ticket, patch, .. Seriously, I mean it!
> > > > Now on to making DataMapper even more awesome!
> > > > cheers
> > > > snusnu
> > > > On Jun 9, 2:07 am, Daniel N <has....@gmail.com> wrote:
> > > >> So very very awesome. :)
> > > >> Congratulations guys, this is really cool.
> > > >> On 9 June 2010 10:04, Dan Kubb (dkubb) <dan.k...@gmail.com> wrote:
> > > >>> I'm pleased to announce that we released DataMapper 1.0 "Vermouth"
> > > >>> earlier today.
> > > >>> Thank you to everyone in the community, especially this mailing list
> > > >>> and the IRC channel. There's no way we could've reached this milestone
> > > >>> without your encouragement and assistance.
> > > >>> It's extremely rewarding to see DM hit 1.0, but at the same time it
> > > >>> also sets a baseline for future development to build on. In some ways
> > > >>> we're only just getting started, the future we have planned for DM is
> > > >>> even more ambitious. I'll be writing more about our plans in the
> > > >>> coming weeks.
> > > >>> Before you install
> > > >>> ------------------
> > > >>> The installation process for DM 1.0 is pretty similar to what it was
> > > >>> previously in 0.10.x and 0.9.x with a few exceptions:
> > > >>> 1) Using auto-migration and auto-upgrading require dm-migrations
> > > >>> rather than just dm-core. The reason for this is that dm-migrations
> > > >>> should share a lot of code with auto-migrations, but they don’t, and
> > > >>> in an attempt to DRY things up we’ve centralized all the code in one
> > > >>> package and will begin refactoring the code over the coming months.
> > > >>> 2) Transactions require the use of the dm-transactions gem.
> > > >>> 3) It is no longer necessary to gem install data_objects or any do_*
> > > >>> gem directly. Each DO based adapter has been extracted into their own
> > > >>> gems, and installing them will setup the dependencies on dm-core and
> > > >>> the appropriate DO gem(s). The new adapters are:
> > > >>> The next thing you want to do is decide which adapter you want to use.
> > > >>> For example if you want to use sqlite, do:
> > > >>> $ gem install dm-sqlite-adapter
> > > >>> This should pull in data_objects and do_sqlite3 automatically, so no
> > > >>> need to specify either of those explicitly anymore.
> > > >>> It’s likely you’ll want to use migrations (for classic or auto-
> > > >>> migrations), and transactions when using sqlite, so to install them
> > > >>> do:
> > > >>> In previous release announcements I've provided details about the
> > > >>> changes, so I'm not going to repeat myself ;) Instead I'm going to
> > > >>> refer you to the list of 61 tickets we've resolved for the 1.0
> > > >>> milestone:
> > > >>> --
> > > >>> You received this message because you are subscribed to the Google Groups
> > > >>> "DataMapper" group.
> > > >>> To post to this group, send email to datamapper@googlegroups.com.
> > > >>> To unsubscribe from this group, send email to
> > > >>> datamapper+unsubscribe@googlegroups.com<datamapper%2Bunsubscribe@googlegrou ps.com>
> > > >>> .
> > > >>> For more options, visit this group at
> > > >>>http://groups.google.com/group/datamapper?hl=en.
> > > > --
> > > > You received this message because you are subscribed to the Google Groups "DataMapper" group.
> > > > To post to this group, send email to datamapper@googlegroups.com.
> > > > To unsubscribe from this group, send email to datamapper+unsubscribe@googlegroups.com.
> > > > For more options, visit this group athttp://groups.google.com/group/datamapper?hl=en.
> > --
> > You received this message because you are subscribed to the Google Groups "DataMapper" group.
> > To post to this group, send email to datamapper@googlegroups.com.
> > To unsubscribe from this group, send email to datamapper+unsubscribe@googlegroups.com.
> > For more options, visit this group athttp://groups.google.com/group/datamapper?hl=en.
> yes, it is in the correct place. > with the dm 0.10.2, was working correctly, I suppose it is something > with this version.
I'm pretty sure this is a 1.9.0 problem. 1.9.1 was the first version released as a stable version, so we've only tested with 1.9.1 and higher. A lot of stuff has changed from 1.9.0 to 1.9.1 and also from 1.9.1 to the upcoming 1.9.2. I'd strongly suggest upgrading at least to 1.9.1 to be able to run DataMapper (and also other 1.9 compatible software).
> yes, it is in the correct place. > with the dm 0.10.2, was working correctly, I suppose it is something > with this version.
I'm pretty sure this is a 1.9.0 problem. 1.9.1 was the first version released as a stable version, so we've only tested with 1.9.1 and higher. A lot of stuff has changed from 1.9.0 to 1.9.1 and also from 1.9.1 to the upcoming 1.9.2. I'd strongly suggest upgrading at least to 1.9.1 to be able to run DataMapper (and also other 1.9 compatible software).
> > yes, it is in the correct place.
> > with the dm 0.10.2, was working correctly, I suppose it is something
> > with this version.
> I'm pretty sure this is a 1.9.0 problem. 1.9.1 was the first version released as a stable version, so we've only tested with 1.9.1 and higher. A lot of stuff has changed from 1.9.0 to 1.9.1 and also from 1.9.1 to the upcoming 1.9.2. I'd strongly suggest upgrading at least to 1.9.1 to be able to run DataMapper (and also other 1.9 compatible software).
