Re: Query.setRefreshingObjects(boolean)

All of my exceptions are at runtime. :-) On Mon, May 5, 2008 at 6:21 PM, Mike Kienenberger <[EMAIL PROTECTED]> wrote: > You don't have to declare the throw clause if it's a RuntimeException. > The method signature doesn't have to change.

Re: Postgresql

On 6. mai. 2008, at 17.43, Eric Polino wrote: We were using derby and have decided to switch to postgresql. I have changed all my adapters and drivers and they seem to be working properly. I'm getting issues when I try to run my initialization script that has always worked before. What issu

Re: Postgresql

Eric, May be the tables are hidden under some schema ? PostgreSQL organizes as a database with multiple schemas (like oracle). The search_path internal postgresql variable defines the schema "search order" to find elements. To find the available structure of your database y recommend to use pga

RE: Query.setRefreshingObjects(boolean)

Of course, how could I forget! Regardless, what's the point of providing API that compiles and then ambiguously breaks? -Original Message- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Monday, May 05, 2008 6:21 PM To: user@cayenne.apache.org Subject: Re: Query.setRefreshingObj

Re: Postgresql

This may not matter for your setup, but is the username "sa" correct? With PostgreSQL, you typically create a "postgres" database superuser. On Tue, May 6, 2008 at 11:43 AM, Eric Polino <[EMAIL PROTECTED]> wrote: > We were using derby and have decided to switch to postgresql. I have > changed al

Postgresql

We were using derby and have decided to switch to postgresql. I have changed all my adapters and drivers and they seem to be working properly. I'm getting issues when I try to run my initialization script that has always worked before. It's a pretty simple script. It's just a whole bunch of inse

Commit with validation errors in detail table

Hi I have a 2 tables with a One-to-many relations. (Master-Details) My code insert one row in the Master table and many rows in the Details table at the end I do a dataContext.commitChanges(); But in some rows in the Details table I have some Validation failures Finally I have no row commited i

RE: Specifying PK when creating a new object in DB generated PK mode

Works great; thanks Andrus. -Original Message- From: Andrus Adamchik [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 06, 2008 4:30 AM To: user@cayenne.apache.org Subject: Re: Specifying PK when creating a new object in DB generated PK mode How about using a brute force approach. You have a

Re: Specifying PK when creating a new object in DB generated PK mode

On May 6, 2008, at 1:07 AM, Scott Anderson wrote: I was looking through my old emails, and I realized that I still haven't found a resolution to this. Andrus vaguely mentioned that there might be a good reason why you aren't allowed to, but I wasn't able to find that reason. So, to recap

many-to-many mapping resulting in incomplete SQL queries

Hello everyone! I am new to cayenne and experiencing some problems, when modelling a many-to-many relationship. After I could not solve the problem for an application I am writing at the moment, I set up the following example application, which is producing the same problems: I modelled a sm

Re: Newbie question about to-many ordered list

As a side note pre-ordered relationships have been on our TODO list for some time. Since it is a JPA feature, it is higher priority now. Andrus On May 6, 2008, at 10:52 AM, Malcolm Edgar wrote: I tend to do this: public List getCustomers() { List customers = super.getCustomers(); Col

Re: Newbie question about to-many ordered list

I tend to do this: public List getCustomers() { List customers = super.getCustomers(); Collections.sort(customers, new StringComparator(Customer.NAME_PROPERTY)); return customers; } regards Malcolm Edgar On Tue, May 6, 2008 at 4:58 PM, Aristedes Maniatis <[EMAIL PROTECTED]> wrote: