Hi David,
Thanks for Help ERModern xxx work nice. I love it.
I really thank you for your hard work to make that, and helps developing time
do get down a lot.
I think my wife will love it, because I can spend more time with her now^^
Everything works great and with your Help I know now what the
Hi,
I've noticed that MIgrations code does not respect the default values
specified. E.g. Following code creates a database table called CALENDAR.
ERXMigrationTable calendarTable = database.newTableNamed(CALENDAR);
calendarTable.newStringColumn(CAL_DESC, 512, true);
default values is not supported by eof directly ... it's up to your database
plugin to support wonder's extension for this to work. currently i believe only
frontbase and postgresql migrations support this.
ms
On Sep 18, 2010, at 4:17 PM, Farrukh Ijaz wrote:
Hi,
I've noticed that
Hi Mike,
Thanks for your prompt reply. We are using Postgresql and I am talking about
the SQL insert statement which gives me error when I execute using Aqua Studio
or PSQL tool.
Do you think I am missing something? Well this is not a show stopper and I can
create an extra version to execute
are you using an up-to-date postgresql plugin from Wonder?
in PostgresqlExpression:
public void addCreateClauseForAttribute(EOAttribute attribute) {
NSDictionary userInfo = attribute.userInfo();
Object defaultValue = null;
if (userInfo != null) {
defaultValue =
I'm afraid I am using an older version. I will update it tomorrow. Hopefully
this will resolve the issue.
Thanks,
Farrukh
Sent from my iPhone
On 2010-09-18, at 11:40 PM, Mike Schrag msch...@pobox.com wrote:
are you using an up-to-date postgresql plugin from Wonder?
in
Hola Mike,
could you please pontime there directly witha link?
I would like to read about it...
regards all ;^)
Dino
On 15 Sep 2010, at 4:18 PM, webobjects-dev-requ...@lists.apple.com
wrote:
Message: 9
Date: Wed, 15 Sep 2010 16:50:51 -0400
From: Mike Schrag msch...@pobox.com
Subject:
I have to update a whole bunch of objects. Method 1 says make a list of the
objects, make the changes and saveChanges(). Seems really inefficient. If there
were only 50 objects I would probably do that. So I created a procedure on
backend. Basically, an update of all records that match a job
try adding
public String _columnCreationClauseForAttribute(EOAttribute attribute) {
return addCreateClauseForAttribute(attribute).toString();
}
public StringBuffer addCreateClauseForAttribute(EOAttribute
eoattribute) {
EOSQLExpression
