Magritte3 and persistence?

I've read in soem tutorial (don't remember which right now) that magritte
have support for data persistency.

If I did not understood it bad, it would mean that it can autogenerate SQL
queries from descriptions so they don't need to be coded manually into the
database class methods, but just could not find any info and/or examples
regarding it.

Can someone point me in the right direction, or tall me if I understood it
bad?

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

There was a, now outdated, Magritte-GLORP integration, to generate
GLORP descriptors based on Magritte metadata.

But as I say it is outdated, and it probably won't work with the
latest Magritte version (3.x) that uses descriptors on the instance
side.

Regards!


Esteban A. Maringolo


2015-01-17 12:34 GMT-03:00 David Carlos Manuelda <[hidden email]>: _______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On Sun, Jan 18, 2015 at 02:16:01PM -0500, John McKeon wrote:
> Magritte-Roe in the Magritte1Addons
> <http://source.lukas-renggli.ch/magritteaddons/>repository might be what
> you want. It requires ROE <http://www.squeaksource.com/ROE> and PostgresV2
> <http://www.squeaksource.com/PostgresV2> packages from squeaksource as well
> as PostgreSQL db installed.

ROE does not support creating new tables in the underlying database, based on
my making ROE work with NBSQLite3. Yes, one could use SQL to do the things ROE
doesn't, but then one now has to deal with two ways of talking to the SQL
database.

Pierce
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside