It is never safe to pull from trunk. ;-) when it is safe I move it to
stable....
by the way I added support for circular references:
db.define_table('a',Field('name'),Field('b','reference b'))
db.define_table('b',Field('name'),Field('a','reference a'))
db.define_table('c',Field('name'),Field('c','reference c'))
at the expense of no check for broken reference
db.define_table('a',Field('name'),Field('b','reference d'))
cannot check if the reference if broken since d may or may not be
defined.
will be in trunk later in the day.
On May 25, 1:29 pm, "David J." <[email protected]> wrote:
> Thanks Massimo;
>
> Sounds good;
>
> Perhaps you can also let us know when it is safe to pull from Trunk for
> those using trunk in production.
>
> Thanks.
>
> David
>
> On 5/25/11 2:20 PM, Massimo Di Pierro wrote:
>
>
>
>
>
>
>
> > There is a new feature in trunk that needs tests and CAN mess up your
> > database metadata so...
>
> > 1) remember - user trunk at your own risk
> > 2) it would be great if you could test it but make sure you backup
> > your metadata (databases/*.table) first
> > 3) if you upgrade to trunk please let me know if you encounter any
> > problem with existing apps on upgrade
>
> > What is the new feature? It changes the format of the databases/
> > *.table metadata to a more verbose format. Why? Because this will
> > allow to open a database from a script without having to run the
> > models. Web2py will be able to discover the metadata and rebuild the
> > table definitions automatically.
>
> > This is half done but needs a little more work and testing.
>
> > Massimo
