It's a new feature as well as a work in progress. Feel free to jump
in and implement improvements and bug fixes and documentation. Those
who will make active use of the functionality are in the best position
to fix it.
On Thu, Apr 9, 2009 at 5:00 PM, Weddle, Anthony
wrote:
> Wow, the speed of
Wow, the speed of response on this list is awesome!
My apologies. The documentation is not clear on this and I didn't
explore enough. I was expecting bot "To DB" and "To Model" operations to
appear and didn't realise that I had to change the direction by clicking
the appropriate cell. (By the way,
If you click the 'to db' it will let you select a new option 'to model' and
reverse the relationship.
J
Sent via BlackBerry by AT&T
-Original Message-
From: "Weddle, Anthony"
Date: Fri, 10 Apr 2009 08:14:58
To:
Subject: RE: Reengineering Overwrites
Sorry, Robert, but I don't get an
Right, so, if you click on "To DB", you should be able to change that
to "To Model", right?
I just tried it... although I was using a snapshot version of the
modeler, so take ti with a grain of salt. :)
Robert
On Apr 9, 2009, at 4/93:14 PM , Weddle, Anthony wrote:
Sorry, Robert, but I don't
Sorry, Robert, but I don't get any operations that have the direction of
DB to map. For example, using the a Derby database, I added an attribute
to a table called "EXTRA", in Modeler, and added a new table,
"RESTAURANTS", to the database (using ij in Eclipse). These are the
operations that Migrate
As a follow on, it will also allow you to save the resulting SQL from
the set of operations you choose. I find this handy for working with
development vs. production servers.
I'll accumulate a list of SQL changes made in development (mind you, I
usually work from the model => db direction, s
Check out the "direction" column of the "Select Operations" table. It
will allow you to choose the direction of the change, and thereby
alter the operation performed (if there's a relationship in the
modeler but not in the db, then to db direction will add a
relationship to your db, and ch
Thanks for the tip, John and Robert. However, I'm not sure that reverse
capability is there in 3.0M5. If I select Migrate DB, I only get
operations in the direction of the database to select. For example, I
altered a table in the map and also added a table on the database; the
two operations that M
Robert, thanks for your advises, appreciated.
I finally made my own EJBQLTemplateQuery using velocity. This works for me.
Still, I'm intrigued by the idea of being able to directly script
> EJBQLQuery. Anybody else think that's interesting? If there's a favorable
> consensus, I'll add an issue an
On Apr 9, 2009, at 11:47 AM, Robert Zeigler wrote:
Now that I'm thinking about this more... even though EJBQLQuery
doesn't support the above scheme, there's no reason you can't tap
into velocity yourself to accomplish what you want.
Exactly my thoughts.
Still, I'm intrigued by the idea of
I think the main problem with trying to use parameters the way you are
with EJBQLQuery is the meaning of "parameters": they're supposed to be
bound to SQL types.
At the same time, the "column names" are really object property names,
which means they have to be translated at the time the query
I already use a lot of SelectQuery and even some SQLTemplate.
My problem with SelectQuery is the fact that it fetches all columns
information for a table and so, can be expensive for specific needs where I
need high performances (here only need ids, so only 1 column to return
rather than 25 -> mor
12 matches
Mail list logo
