I use lazy tables so all the foreign keys in my model are defined with forward reference syntax. I am using PostgreSQL for the database. I have to qualify that the schema is unchanged and the tables are as they were before trying trunk. Previous version in use was 2.2.1. The application I am working on runs without issues on trunk in all other aspects.
The only problem I have had is I use jQueryDatePlusTimePicker which is layered over jQueryUI DatePicker. I have not found a way to bring in the new Twitter bootstrap layout system, the jQueryUI buttons function but don't render due to a conflict. I have remained on the Superfish menu system and layout. This has nothing to do with 2.3.1 since it is common to all 2.X releases and is a problem I need to solve. Ron On Wednesday, 5 December 2012 01:50:20 UTC-8, Joe Barnhart wrote: > > I think there is a problem with forward-referenced tables, at least when > using Postgres. > > I tried the trunk release on Postgres today (for the first time) and > noticed that it would not take any tables defined with forward references > (using Field 'xxx' 'reference yyy' syntax). If I moved the tables around > until there were no forward references it worked fine. It also worked fine > when I was using sqlite before switching to Postgres, but the tables had > already been defined so I'm not sure that was a valid test. > > I was not sure this had anything to do with the version in trunk until I > came home tonight and tried the same experiment on the current release. > Forward references worked just fine on version 2.2.1 with Postgres and > Sqlite. > > -- Joe B. > > On Monday, December 3, 2012 2:39:15 PM UTC-8, Massimo Di Pierro wrote: >> >> Please check the nightly build. I would like to release 2.3.1 asap, later >> this week. >> >> Massimo >> > --
