Hi Esteban,
thank you for the solution with the VOMongoToOneDescription.
This works perfect for me.
I have to come back to the circular references.
I am not sure if this is a bug.
I have the following model:
Trip ->> Day <->> VehicleTrip
One Trip has N Days.
One Day has N VehicleTrips.
The Veh
On Wed, Jul 31, 2013 at 6:27 PM, joerick wrote:
> In the Gofer #push case, it's quite strange... some classes end up the
> wrong
> package, and some don't get output at all.
>
> It seems to work using Gofer #push when each is in its own repository
> folder, and it also works with them all in the
On Sat, Aug 10, 2013 at 11:44:06PM +1000, vin...@gmail.com wrote:
> VoyageMongo looks interesting. PostgreSQL is supported too. Do either of
> these work through FFI?
On SqueakSource, PostgresV2, PostgresV3, MySQL and StdbCore (for MySQL) are
pure Smalltalk implementations of the respective wire p
Hi Sabine,
Sadly there is no automatic solution for your problem.
I managed to resolve that by hacking the mongo description this way:
Trip class>> isVoyageRoot = true
Day class>> isVoyageRoot = false
VehicleTrip class>> isVoyageRoot = false
Now, the trick is that since the document will be
