A new release of Madeleine is now available. There has been a lot of
internal changes since the last release, but the user-visible changes
are (hopefully) limited to the ones listed below.
News in Madeleine 0.6:
* Changed license to BSD
* Added a RubyGem specification
* Re-designed initialization (but still backward-compatible)
* Bug fix: Fixed use of finalized object's id in AutomaticSnapshotMadeleine
Within the next few minutes, madeleine 0.6 should be available via:
gem --remote-install madeleine
Chad
···
On 28/3/2004, at 11:09 AM, Anders Bengtsson wrote:
News in Madeleine 0.6:
* Changed license to BSD
* Added a RubyGem specification
* Re-designed initialization (but still backward-compatible)
* Bug fix: Fixed use of finalized object's id in
I’m thrilled to see that you’re still working on Madeleine. I use it as
the foundation for Instiki[1] and plan to use it in an upcoming
commercial project as well.
Regarding Instiki, I’ve received some mails from Windows users that
tells me that their Madeleine storage sometimes corrupts. I remember
reading somewhere that this was a known problem with Madeleine. Does
any of these fixes relate to this problem?
P.S.: Do you have a road map or even an idea of future features for
Madeleine?
Hi Anders, what are the steps in Madeline to create a simple website, e.g
1- connect to mysql db
2- get the data from mysql database and display them in a table form with
simple formatting
3- (future) search/add/modify/delete
On Mon, 29 Mar 2004 04:38:08 +0900 David Heinemeier Hansson david@loudthinking.com wrote:
News in Madeleine 0.6:
I’m thrilled to see that you’re still working on Madeleine. I use it as
the foundation for Instiki[1] and plan to use it in an upcoming
commercial project as well.
Regarding Instiki, I’ve received some mails from Windows users that
tells me that their Madeleine storage sometimes corrupts. I remember
reading somewhere that this was a known problem with Madeleine. Does
any of these fixes relate to this problem?
P.S.: Do you have a road map or even an idea of future features for
Madeleine?
I’m thrilled to see that you’re still working on Madeleine. I use it
as
the foundation for Instiki[1] and plan to use it in an upcoming
commercial project as well.
Cool to see it being used! I’ll take a look at Instiki.
Regarding Instiki, I’ve received some mails from Windows users that
tells me that their Madeleine storage sometimes corrupts. I remember
reading somewhere that this was a known problem with Madeleine. Does
any of these fixes relate to this problem?
There was a problem with the logs being read in the wrong order in an
older version of Madeleine, which was fixed in a previous release. Then
there is apparently a problem with text vs. binary-mode still in the
current version. There was a two-line patch for this posted to the
madeleine-devel mailing list, so I’ll make a new release in the next
few days.
P.S.: Do you have a road map or even an idea of future features for
Madeleine?
There are some scattered thoughts in the TODO file, but no grand plan.
Madeleine isn’t a web library, it’s a persistence library. So you would
typically use it instead of MySQL.
If you’re still interested, I think Instiki
(http://instiki.rubyforge.org/) may be a good example for how you can
use Madeleine for a website.
Hi Anders, what are the steps in Madeline to create a simple website,
e.g
1- connect to mysql db
2- get the data from mysql database and display them in a table form
with
simple formatting
3- (future) search/add/modify/delete
=====
Anders Bengtsson ndrsbngtssn@yahoo.se
Stockholm, Sweden
Hi Anders, what are the steps in Madeline to create a simple website, e.g
1- connect to mysql db
2- get the data from mysql database and display them in a table form with
simple formatting
3- (future) search/add/modify/delete
Madeleine is not library to connect to a SQL database. Madeleine is a
Ruby implementation of the Prevayler persistence pattern (serialized
object model in memory, altered through command objects).
It sounds like an in-memory database of Ruby objects that knows how to
keep itself synced out to disk so that from program run to program run the
objects stay persistent.
Pstore with more magic?
Kirk Haines
···
On Thu, 1 Apr 2004, Paul Brannan wrote:
On Mon, Mar 29, 2004 at 01:09:24AM +0900, Anders Bengtsson wrote:
What is Madeleine?
After reading the webpage, I’m still wondering that.
Perhaps I missed it, but I see no example code (there’s some in CVS; it
would be nice if there were links to it on the main page).
gpl:
use it and change it, but if you sell you changed version, make the
source available under gpl.
lgpl:
same as gpl, but used, usually, for libs. If your code links against
lgpl you don’t need to release it under lgpl, you can use closed
license. But if you change the library , is the same as gpl.
bsd:
same as gpl, but you do not need to show the changed sources. You
just need to give credit to the older author.
On Wednesday 31 March 2004 10:34, Kirk Haines wrote:
What is Madeleine?
After reading the webpage, I’m still wondering that.
It sounds like an in-memory database of Ruby objects that knows how to
keep itself synced out to disk so that from program run to program run the
objects stay persistent.
It sounds like an in-memory database of Ruby objects that knows how to
keep itself synced out to disk so that from program run to program run the
objects stay persistent.
Pstore with more magic?
It has some similarities with Pstore, but not that many. It has a very
different architecture and does transactions much faster.
And yes, it has more magic!
If a consultant use any of those program with the above license at his/her
client(for its website), would that violate the licensing agreement(since
it’s commercial)?
What’s the significant difference between GPL, Lesser GPL, and BSD
Licensing?
you’re stimulating a huge flamewar
gpl:
use it and change it, but if you sell you changed version, make the
source available under gpl.
lgpl:
same as gpl, but used, usually, for libs. If your code links against
lgpl you don’t need to release it under lgpl, you can use closed
license. But if you change the library , is the same as gpl.
bsd:
same as gpl, but you do not need to show the changed sources. You
just need to give credit to the older author.
I’ve been doing some reading on it. It seems very interesting, and I can
certainly see some useful applications for it. My naive reaction is that
it is too bad that there isn’t some way of not having everything loaded in
memory all at the same time, but at the same time, I can think of a
several different applications that I have running right now that might,
at least theoretically, benefit from Madeleine. I need to learn more.
Thanks,
Kirk Haines
···
On Thu, 1 Apr 2004, Anders Bengtsson wrote:
It has some similarities with Pstore, but not that many. It has a very
different architecture and does transactions much faster.
And yes, it has more magic!
None of them have a no-commmercial-use clause – you can do whatever you
like with them, as long as you follow the provisions in the license –
for the GPL and LGPL, you have to contribute changes back (which depends
on the license) and give credit. The BSD license just asks for credit.
Ari
···
On Tue, Mar 30, 2004 at 12:44:23AM +0900, Useko Netsumi wrote:
If a consultant use any of those program with the above license at his/her
client(for its website), would that violate the licensing agreement(since
it’s commercial)?
