Re: A note on postgres multitenat implementation with 1 schema per tenant

I recently had a similar problem that required setting a default connection *catalog* (this was on MySQL that does not support schemas). I solved that with a custom DataSource wrapper per stack [1]. However JDBC connection class does not have a notion of default schema, so this will not work wit

Re: 3.2M1 first impressions

Hi, Thanks for the feedback! Good to have that for 3.2. > all the generics code uses just T as "T extends Object" and not "T extends > DataObject" (or maybe another superinterface wich makes sense) Some of it is because query result can be a DataRow, or an Object[]. Other places (like “delet

Re: 3.2M1 first impressions

objectForQuery = ObjectContext.selectOne I'm not in front of the code right now, but I believe the type parameter is unbounded to allow for fetching data rows as well, which are not DataObjects or Persistent or anything. John On Mon, Nov 11, 2013 at 11:48 AM, Ramiro Aparicio < ramiro.apari...@p

3.2M1 first impressions

Hi, I am doing today my usual updated maven depencies for our future product release, so I am migrating my 3.1 code to the new 3.2 generics style and I missed that all the generics code uses just T as "T extends Object" and not "T extends DataObject" (or maybe another superinterface wich mak