<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Thank you very much guys.<br>
Marco, I know GOODS is an excellent oodb, it's been used in my company
with great success (in a C++ comertial project). <br>
Since I am coding squeak mostly for fun, I wanted to try the *pure*
squeak way, and hence I wanted to give Magma a fair chance. Besides,
I have an "irrational" belief in it (by now at least), and respect for
the impressive undertaking that Chris Müller faced. So before I give
up on it, I want to test it more thoroughly and hear more oppinons of
people using it, there must be more out there...<br>
<br>
So... another important question: <br>
Does Magma support bidirectional relations?<br>
I have a very simple situation where it all hangs. Is a very simple
line, that commits a class which holds a collection of elements that
also have a reference to the main class. Its so simple that I can't
find any other explanation.<br>
Thanks again.<br>
<br>
<br>
r.<br>
<br>
<br>
<br>
<br>
<br>
<pre class="moz-signature" cols="72">--
Ramiro Díaz Trepat
<a class="moz-txt-link-freetext" href="http://novamens.com">http://novamens.com</a>
<a class="moz-txt-link-freetext" href="http://neosmt.com">http://neosmt.com</a></pre>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:goran.krampe@bluefish.se">goran.krampe@bluefish.se</a> wrote:<br>
<blockquote cite="midE1Bfv1R-0007pQ-00@leia.bluefish.se" type="cite">
<pre wrap="">Hi!
Marco Paga <a class="moz-txt-link-rfc2396E" href="mailto:seaside@marco-paga.de"><seaside@marco-paga.de></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I had problems with Magma too. I switched to goods OO database and it's really
working without any problems. You just read some examples and you can start
using it.
</pre>
</blockquote>
<pre wrap=""><!---->
Nothing wrong with GOODs of course, I played with it a bit and Jonas
here is actually migrating a Hibernate app over to GOODs - will be very
interesting to see the results, especially compared to Hibernate which
people are so excessively worked up about. ;)
But I have also used Magma, and I have had almost no problems.
</pre>
<blockquote type="cite">
<pre wrap="">Am Mittwoch, 30. Juni 2004 16:53 schrieb Ramiro Diaz Trepat:
</pre>
<blockquote type="cite">
<pre wrap="">Does anybody have a more detailed guide or code examples on using Magma
than what is on the main Squeak Swiki?
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
Eh, no. :) But I am making a demo app that uses Magma. Though I am not
sure when it will be ready for "consumption".
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">I am running into problems, at a very eary stage, and I am almost sure
that these problems are caused because of my meager knowledge on how to
use the framework.
For example, all the collections held as attributes by classes that you
intend to persist should be MagmaCollections?
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
No, that is not needed. You can use MagmaCollections if you want the
features they give though. I haven't used them yet.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">How does the fact of using Magma affect the code and development
process? What are the most important things to keep in mind?
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
Well, since I haven't done a lot with Magma yet - but I do have some
experience with OOdbs in general. Object migration is likely the most
"tricky" part. Which means the problem of migrating you old objects over
to new evolved classes. I haven't seen exactly what limitations Magma
has in that respect - though I think it can handle some cases.
A general technique that might be useful though is if you have an
import/export format of some kind that will not evolve. One system I
built needed XML import/export for a large sub part of the domain model.
We used that feature to be able to "reload" test data into an empty db
during development.
So in short - having a test db that can be recreated from either
external files of from "instantiation code" can be a real time saver
during development. Then the problem of object migration will not rear
its ugly head until after the first deployment. :)
Note: The above technique is not specific for OOdbs, IMHO it applies
equally well to any system with persistent data.
Finally - the development process with Magma is IMHO more or less like
pretending you are only working in RAM. :) You just sprinkle your
application code (NOT your domain model) with some suitable
begin/commits.
regards, Göran
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">
</pre>
</body>
</html>