a WODisplayGroup).
>
> Thanks a lot again,
> OC
>
>> On 15. 2. 2022, at 0:29, Samuel Pelletier > <mailto:sam...@samkar.com>> wrote:
>>
>> Hi,
>>
>> As Aaron wrote, ERExisitsQualifier will generate an SQL for your needs. You
>> may also
As Aaron wrote, ERExisitsQualifier will generate an SQL for your needs. You
> may also change the JOIN type to change it's behaviour in SQL. EOF apply
> table joins before qualifier, I suspect other ORM does the same too.
>
> For that kind of quarry, you will probably have better pe
Hi,
As Aaron wrote, ERExisitsQualifier will generate an SQL for your needs. You may
also change the JOIN type to change it's behaviour in SQL. EOF apply table
joins before qualifier, I suspect other ORM does the same too.
For that kind of quarry, you will probably have better performance
wrote:
>
> Hi there,
>
> lately, I am encountering wrong fetches (with FrontBase, if important). I log
> out my qualifier and SQL, and the gist of the problem is a join in the
> OR-part of the qualifier. I want to fetch rows where there's an empty
> attribute, OR when the
Hi OC,
That’s called the object to relational impedance mismatch. The qualifier works
in memory but fails when you try to invoke with SQL.
To get around it, you can use an ERXExistsQualifier for your to-one
relationship. Typically you use this with to-many relationships but it actually
can
Hi there,
lately, I am encountering wrong fetches (with FrontBase, if important). I log
out my qualifier and SQL, and the gist of the problem is a join in the OR-part
of the qualifier. I want to fetch rows where there's an empty attribute, OR
when there's a specific join:
06:52:06
ote:
>>>
>>> Hi Gino:
>>>
>>> I think I might have seen this error when the MySQLPlugin is not in the app
>>> classpath? In other words, some SQL that the frameworks are trying to build
>>> for a transaction are subsequently not
36, Tim W wrote:
>>
>> Hi Gino:
>>
>> I think I might have seen this error when the MySQLPlugin is not in the app
>> classpath? In other words, some SQL that the frameworks are trying to build
>> for a transaction are subsequently not being customized prope
m W wrote:
>
> Hi Gino:
>
> I think I might have seen this error when the MySQLPlugin is not in the app
> classpath? In other words, some SQL that the frameworks are trying to build
> for a transaction are subsequently not being customized properly for MySQL
> before being
Hi Gino:
I think I might have seen this error when the MySQLPlugin is not in the app
classpath? In other words, some SQL that the frameworks are trying to build for
a transaction are subsequently not being customized properly for MySQL before
being sent to the DB.
The errors makes sense in
Isn’t that just when the adaptor needs to reconnect after a period of rest?
> On Feb 4, 2020, at 4:00 PM, Gino Pacitti via Webobjects-dev
> wrote:
>
> Hi
> Has anyone encountered this sort of error before?
>
> It does not happen all the time but just on occasion.
>
> mysql Ver 14.14 Distrib
Gino,
I can be completely wrong, but it looks like two problem logs interspersed,
which stinks by a threading issue, along with the fact it happens
intermittently.
If possible, I'd check race conditions and try to synchronize (or lock) where
needed.
Quite possibly someone other would give a m
Hi
Has anyone encountered this sort of error before?
It does not happen all the time but just on occasion.
mysql Ver 14.14 Distrib 5.7.28, for Linux (x86_64) using EditLine wrapper
Java 8
mysql-connector-java-8.0.19.jar
This is my connection URL
jdbc:mysql://127.0.0.1/_UTF_8?capitalizeTypeN
Useful Resource :
https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-reference-configuration-properties.html
> On 14 Oct 2018, at 15:02, Gino Pacitti wrote:
>
> use sendFractionalSeconds=false in the connection string :)
>
>> On 14 Oct 2018, at 12:46, Gino Pacitti wrote:
>>
>> Im loo
use sendFractionalSeconds=false in the connection string :)
> On 14 Oct 2018, at 12:46, Gino Pacitti wrote:
>
> Im looking and looking but the error seems to be here:
>
> Invocations of setNanos() are illegal.
> java.lang.IllegalStateException: com.webobjects.foundation.NSTimestamp is an
> imm
Im looking and looking but the error seems to be here:
Invocations of setNanos() are illegal.
java.lang.IllegalStateException: com.webobjects.foundation.NSTimestamp is an
immutable object. Invocations of setNanos() are illegal.
at com.webobjects.foundation.NSTimestamp.setNanos(NSTimestam
We got the same problem. Any solution yet?
Best regards,
Daniel Bietenbeck
> Am 14.10.2018 um 13:06 schrieb Gino Pacitti :
>
> I just updated my mysql server on linux and columns which are DATETIME and
> when I am using NSTimestamp for Qualifiers for a query (plus any inserts with
> a NSTimes
Could it be something to do with this:
https://dev.mysql.com/doc/refman/5.6/en/datetime.html
Where Mysql is trying to find microseconds?
Gino
> On 14 Oct 2018, at 12:06, Gino Pacitti wrote:
>
> I just updated my mysql server on linux and columns which are DATETIME and
> when I am using NSTim
I just updated my mysql server on linux and columns which are DATETIME and when
I am using NSTimestamp for Qualifiers for a query (plus any inserts with a
NSTimestamp) are causing errors:
com.webobjects.foundation.NSTimestamp is an immutable object. Invocations of
setNanos() are illegal.
I ha
Anyone getting the failure Exception below, while using EOModeler to generate
SQL and executing
fetches eg: ERXDatabaseContext._objectsWithFetchSpecificationEditingContext ?
I suspect the PostgresqlPlugIn.framework and associated PlugIn are out of date.
Thanks,
Kwasi
PSQLException: This
What version of MySQL did you upgrade to? I have an xserve running MySQL and
was thinking about upgrading.
Steve
> On Jun 28, 2016, at 3:13 PM, Musall Maik wrote:
>
> PostgreSQL runs fine on OS X. I recommend homebrew to manage the software
> installation, which lets you easily choose which
PostgreSQL runs fine on OS X. I recommend homebrew to manage the software
installation, which lets you easily choose which version you want, pin certain
versions and so on.
The only caveat that I know of is when you run pg on another platform, say
Linux, in production, and use an OS X server as
Hi,
my intranet applications runs for some years on mysql. But now it
seems the new version of mysql and Mac OS X Yosemite are no
longer compatible. The database opens tables but never closes them
and after some time throws exceptions (too many open files). I tried
what I found
on the web bu
To format a date as a varchar with zero-padded month and day, here’s a SQL
select snippet that works for me in Postgres 9.3, but I think it should work in
FrontBase maybe with a little fiddling of syntax such as substring(’00’ ||
‘1234’ from 3 for 2) where starting position is 3, and the number
...
>
> On 11. 3. 2016, at 22:06, OC wrote:
>
>> Still, it can be solvable (perhaps even easily)
>>
>> (a) in standard SQL92 which I don't know well enough
>> (b) in some FrontBase-specific extension
>>
>> which is why I am asking.
>
> ...
Well...
On 11. 3. 2016, at 22:06, OC wrote:
> Still, it can be solvable (perhaps even easily)
>
> (a) in standard SQL92 which I don't know well enough
> (b) in some FrontBase-specific extension
>
> which is why I am asking.
... without better knowledge the SQL used
looks like my iphone didn't decoded from base64, weird
> On 11 mar 2016, at 21:58, Chuck Hill wrote:
>
> The message looked fine to me both on my iPhone and in my mail client.
>
>
>
>
> On 2016-03-11, 12:52 PM,
> "webobjects-dev-bounces+chill=gevityinc@lists.apple.com on behalf of
> A
Chuck,
On 11. 3. 2016, at 21:59, Chuck Hill wrote:
> It is supposed to be SQL92 compliant. If standard SQL can’t do it, you might
> be out of luck.
I am no SQL guru myself; the google results look like there is a terrible mess
of standard- and server-specific tools. Eg., there seems
It is supposed to be SQL92 compliant. If standard SQL can’t do it, you might
be out of luck. This is not something you can do client-side?
Chuck
On 2016-03-11, 12:47 PM,
"webobjects-dev-bounces+chill=gevityinc@lists.apple.com on behalf of OC"
wrote:
>Hello there,
>
The message looked fine to me both on my iPhone and in my mail client.
On 2016-03-11, 12:52 PM,
"webobjects-dev-bounces+chill=gevityinc@lists.apple.com on behalf of Amedeo
Mantica" wrote:
>sgvscohsvosvhpveusvvuvssvvubwbwbibebiwbibeubvusv !??
>
>Sent from my iPhone
>
>> On 11 Mar 2016,
sgvscohsvosvhpveusvvuvssvvubwbwbibebiwbibeubvusv !??
Sent from my iPhone
> On 11 Mar 2016, at 21:47, OC wrote:
>
> SGVsbG8gdGhlcmUsCgphbnkgRnJvbnRCYXNlIFNRTCBndXJ1cyBvbi1saW5lPyBGb3IgYSBkZXJp
> dmVkIGF0dHJpYnV0ZSwgSSB3b3VsZCBuZWVkCgotLSAoYSkgdG8gZm9ybWF0IGEgVElNRVNUQU1Q
> IGFzIOKAnCVZJW4lZeKAnQ
Hello there,
any FrontBase SQL gurus on-line? For a derived attribute, I would need
-- (a) to format a TIMESTAMP as “%Y%n%e”
So far the best I have found is
CAST(EXTRACT(year FROM DATE) AS VARCHAR(4)) ||
CAST(EXTRACT(month FROM DATE) AS VARCHAR(2)) ||
CAST(EXTRACT(day FROM DATE) AS VARCHAR(2
Dominique,
Chuck's comment about identity columns cleared all my issues (basically, I
changed the columns to integers). Aside from that, I have not had an issue with
the plug-in using SQL Server 2008 R2.
David
From: Chuck Hill
Sent: Friday, March 4, 2
mailto:ch...@gevityinc.com>> wrote:
On 2014-11-25, 1:12 PM, "Ress, David A" wrote:
Good afternoon,
My current question is a development issue: I am using SQL Server and I cannot
seem to find its plugin framework within the latest Wonder builds listed at
https://github.com/wo
Hi all,
I installed MySQL 5.7 for testing in development machine (OS X 10.11.3),
working so far with MySql 5.6.
MySQL server is on and I can connect by Terminal. But when I try to generate
sql from EOModeler I get the following
Failed to generate sql. Null pointer exception
Details
ed as
prototype id which is an Integer. After I added the idLong to the EOPrototypes
in our EO model for custom prototypes and restarted eclipse a few times the SQL
generation started working.
Thanks!
JR
From: Chuck Hill mailto:ch...@gevityinc.com>>
Date: Thursday, January 14, 2016 at 7:1
Webobjects-dev@lists.apple.com>"
mailto:webobjects-dev@lists.apple.com>>
Subject: WOLips EntityModeler error in SQL generation
I created a new entity that has no relationships to any other entity in my
model and when I select my new entity and click the SQL generation icon in
Entity Mo
I created a new entity that has no relationships to any other entity in my
model and when I select my new entity and click the SQL generation icon in
Entity Modeler shows the error below. WFAttachment is an entity from and old WO
app that is at end of life. Any idea how I can fix this?
[cid
Another related, I think, exception/error associated with Entity Modeler/EOF
implementation of WOLips;
Another Exception [from the Entity Modeler] to support my previous
'difficulty'...:
java.lang.RuntimeException: Failed to genera
gValue(String<http://java.sun.com/j2se/1.5.0/docs/api/java/lang/String.html>
string)
Formats string for use as a string constant in a SQL statement.
EOSQLExpression's implementation encloses the string in single quotes, escaping
any single quotes already present in string.
So as to avoid
E prod.SITE_ID = site.ID AND site.SITE_NAME = '?' AND
>>> ipr.PRODUCT_ID = prod.ID AND ipr.INDUSTRY_ID = ind.ID AND ind.INDUSTRY_NAME
>>> ='ANH' AND prod.PUB_TRIGGER = 'Y' AND ((prod.EXPIRATION_DATE > SYSDATE) OR
>>> (prod.EXPIRATION_DA
>>
>>
>>
>>> On 24.09.2015, at 16:22, Markus Ruggiero >> <mailto:mailingli...@kataputt.com>> wrote:
>>>
>>> Folks,
>>>
>>> What is the preferred way to fetch EOs when you have a db vendor specific
>>> "
EOs when you have a db vendor specific
>> "select id from ... where ." statement?
>>
>> I need to interface with a legacy system where I have to incorporate the
>> functionality of an external java tool into a Wonder app. This external tool
>> executes
t; "select id from ... where ." statement?
>
> I need to interface with a legacy system where I have to incorporate the
> functionality of an external java tool into a Wonder app. This external tool
> executes raw SQL select statements which it reads from a file.
Maybe ERXSQLQueryWithBindingsUtilities could be useful here. You'd still have
to parse the binding values, but at least you'd get to keep the SQL.
Fabian
> Am 25.09.2015 um 00:48 schrieb Chuck Hill :
>
> The challenge is going to be "In addition these statements are
&
and what you are exactly trying to achieve. If
>you just need to run the vendor specific SQL to get a list of primary
>keys that you can then use to fetch the EOs you want you could do
>something like
>
>
>EOEditingContext ec = ERXEC.newEditingContext();
>EOEntity entity = ERXEOAcc
Hi,
For raw row fetches, there is a shorter way:
EOEditingContext ec = ERXEC.newEditingContext();
NSArray rawRows = EOUtilities.rawRowsForSQL(ec, "YourModelName",
sql));
...
Samuel
> Le 2015-09-24 à 14:48, Johann Werner a écrit :
>
> Hi Markus,
>
> I did not cl
Hi Markus,
I did not clearly understand what you are exactly trying to achieve. If you
just need to run the vendor specific SQL to get a list of primary keys that you
can then use to fetch the EOs you want you could do something like
EOEditingContext ec = ERXEC.newEditingContext();
EOEntity
Folks,
What is the preferred way to fetch EOs when you have a db vendor specific
"select id from ... where ." statement?
I need to interface with a legacy system where I have to incorporate the
functionality of an external java tool into a Wonder app. This external tool
execut
PM
To: Chuck Hill mailto:ch...@gevityinc.com>>
Cc: WebObjects Development
mailto:webobjects-dev@lists.apple.com>>
Subject: Re: postgresql eomodeler correctly "generate sql"
Hmmm thank you Chuck for that interesting bit. It does make sense not using
auto increment in the db with
Hi Yuri!
I'm using postgresql 9.3, and I really had no problem in generating SQL.
I had some problems while migrating from my old server, to the new one,
because I used the wrong version of the JDBC driver, but, after correct it,
I don't have other problems.
Should you try to u
key should be is up to it.
Doesn’t that create problems?
I still have problems running the generated sql. I’ll continue to hand build
the db (but without using serial datatypes this time) until someone has an
answer
> On Jul 18, 2015, at 2:25 PM, Chuck Hill wrote:
>
> Hi Yuri,
&
18, 2015 at 10:50 AM
To: WebObjects Development
mailto:webobjects-dev@lists.apple.com>>
Subject: postgresql eomodeler correctly "generate sql"
Greetings everyone,
This is mostly directed to those that use Postgresql.
I'm using postgresql 9.4. In EOModeler using prototypes.
Greetings everyone,
This is mostly directed to those that use Postgresql.
I’m using postgresql 9.4. In EOModeler using prototypes. Everything works fine
other than when I try to generate sql, it seems to be generating it
incorrectly. For example: id is generated with the integer(int4) datatype
aacir...@gmail.com>>
>>> À: "Samuel Pelletier" mailto:sam...@samkar.com>>
>>> Cc: "WebObjects-Dev Mailing List List" >> <mailto:Webobjects-dev@lists.apple.com>>
>>> Envoyé: Jeudi 7 Mai 2015 15:31:32
>>> Objet: Re: Entity
;>
>> De: "Ângelo Andrade Cirino"
>> À: "Samuel Pelletier"
>> Cc: "WebObjects-Dev Mailing List List"
>> Envoyé: Jeudi 7 Mai 2015 15:31:32
>> Objet: Re: Entity Modeler SQL generation exception
>>
>> Hi Samuel, Wolfy seems
letier" mailto:sam...@samkar.com>>
> Cc: "WebObjects-Dev Mailing List List" <mailto:Webobjects-dev@lists.apple.com>>
> Envoyé: Jeudi 7 Mai 2015 15:31:32
> Objet: Re: Entity Modeler SQL generation exception
>
> Hi Samuel, Wolfy seems to have solved the bug.
BTW, the fix from Wolfy also fix the issue with reverse engineering!
- Mail original -
De: "Ângelo Andrade Cirino"
À: "Samuel Pelletier"
Cc: "WebObjects-Dev Mailing List List"
Envoyé: Jeudi 7 Mai 2015 15:31:32
Objet: Re: Entity Modeler SQL generatio
have fixed the problem.
>> Please have a look at the pull-request which should fix it:
>> https://github.com/wocommunity/wolips/pull/116
>> <https://github.com/wocommunity/wolips/pull/116>
>>
>> The description of the problem is added to the pull-request.
&g
t; https://github.com/wocommunity/wolips/pull/116
> <https://github.com/wocommunity/wolips/pull/116>
>
> The description of the problem is added to the pull-request.
>
> Greetz, Wolfy
>
> Subject: Re: Entity Modeler SQL generation exception
> From: aacir...@gmail.c
Hi Wolfy, I guessed the issue could be solved editing the configuration files
as you did, but I used your commit and it raised another problem:
org.objectstyle.wolips.eomodeler.core.model.EOModelException: There was more
than one SQL generator factory defined.
at
Hi Samuel, Wolfy seems to have solved the bug. I will create a branch in my
repo and will report back.
Angelo
> Em 07/05/2015, à(s) 16:25, Samuel Pelletier escreveu:
>
> Ângelo,
>
> I added some debug output and I think I found the problem but have no
> solution yet...
>
> Activator.g
Ângelo,
I added some debug output and I think I found the problem but have no solution
yet...
Activator.getDefault().log("IEOSQLGeneratorFactory object class : " +
o.getClass().getName());
for (Class anInterface : o.getClass().getInterfaces()) {
Activator.getDefa
Hy,
I think I have fixed the problem.
Please have a look at the pull-request which should fix it:
https://github.com/wocommunity/wolips/pull/116
The description of the problem is added to the pull-request.
Greetz, Wolfy
Subject: Re: Entity Modeler SQL generation exception
From: aacir
In IEOSQLGeneratorFactory.java I made this
Object o = configurationElement.createExecutableExtension("class");
System.out.println("object class : " + o.getClass().getName());
IEOClassLoaderFactory classLoaderFactory = (IEOClassLoaderFactory) o;
And got this output
object class :
org.objectstyle
:357)
> at
> org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:568)
> at
> org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
> ... 7 more
> org.objectstyle.wolips.e
The same here, unfortunately I don’t know how to help.
> Em 06/05/2015, à(s) 18:29, Ramsey Gurley escreveu:
>
> This appears related to:
>
> https://github.com/wocommunity/wolips/commit/2e3a8194cff84ae1ea24e7c0608303da65bbf582#diff-a1bbac9aca1f8883cda10fb887d89b7dL18
>
> If I return that to EO
This appears related to:
https://github.com/wocommunity/wolips/commit/2e3a8194cff84ae1ea24e7c0608303da65bbf582#diff-a1bbac9aca1f8883cda10fb887d89b7dL18
If I return that to EOEclipseClassLoaderFactory, I crash with a classnotfound
on EOFSQLGenerator53.
On May 6, 2015, at 11:13 AM, Ramsey Gurley
Uhhhg
Me too
On May 5, 2015, at 9:05 AM, Ângelo Andrade Cirino wrote:
>
> java.lang.ClassCastException:
> org.objectstyle.wolips.eomodeler.eclipse.EclipseEOModelGroupFactory cannot be
> cast to org.objectstyle.wolips.eomodeler.core.model.IEOClassLoaderFactory
> at
> org.objectstyle.wo
This is the exception I got when debugging WOLips 4.4
java.lang.ClassCastException:
org.objectstyle.wolips.eomodeler.eclipse.EclipseEOModelGroupFactory cannot be
cast to org.objectstyle.wolips.eomodeler.core.model.IEOClassLoaderFactory
at
org.objectstyle.wolips.eomodeler.core.model.IEOC
ple, I had
another application once where the table names actually had to be changed
dynamically (not my design!). The schema for most of the tables was repeated
over a hundred times, once for each customer, with a different suffix. Instead
of modeling it over and over I intervened in the SQL gen
Hi Susanne,
For simplicity and backwards compatibility it is not hard to see that the
addition of a schema property isn’t adequate. The externalName (Table Name in
Entity Modeler) property is enough for the issue of getting the schema name.
Angelo
> Em 05/05/2015, à(s) 05:20, Susanne Schneider
List
Subject: On SQL fully qualified names and how to implement them in EO
models
Message-ID: <4a73b037-ffad-42fe-bc47-6f546eab2...@gmail.com>
Content-Type: text/plain; charset="utf-8"
A common practice is to partition the database tables in several different
schem
; TABLE.COLUMN
myAttribute.fullyQualifiedName() => SCHEMA.TABLE.COLUMN
This would spare some work in the composition of the names in the generation of
expressions and SQL code. Also, this methods, as KVC, would be accessible for
every other use that is needed, for example in template parsing.
For me, the more ex
I'm not sure that modifying the plugins to use a UserInfo dictionary entry
would be more likely to cause problems than modifying them to use a new
top-level entry.
There is already a _entityModeler key that is added to the various UserInfo
dictionaries to hold things like multiple connection d
A common problem FrontBase users face with the current plug-in is the generated
SQL for table creation containing malformed named constraints.
A quick and simple solution is to set USE_NAMED_CONSTRAINTS to false in the
FrontBase plug-in source com.webobjects.jdbcadaptor._FrontBase
I submitted
Hi Mark,
I thought about it too, but it would be a non-standard solution, since each
developer could use a name for the property. To be more precise, I abandoned
this idea after working to change the FrontBase plug-in and SQLHelper to use
EOSchemaSynchronizationFactory. The code that will use t
On May 4, 2015, at 6:42 PM, Ângelo Andrade Cirino wrote:
> Another possibility, more explicit and more direct, would be to have a new
> field in Entity Modeler to insert the schema name. This way we would have an
> entity property that could be directly used to build SQL with t
have been thinking about how to deal with fully qualified names in
my EO models. The obvious solution was to use the qualified name SCHEMA.TABLE
in the entity’s "External Name”. But this leads to a cumbersome need to split
the names in every SQL generation method for each specific plugi
I’ve resorted to migrations, but then I had to fix a lot of things to get
migrations working properly.
Fixing this issue of SQL generation demands knowledge of Eclipse plug-in
development that I lack and, from the code I inspected trying to debug the
issue, seems very hard to grasp in a short
n(RegistryStrategyOSGI.java:174)
> ... 7 more
> org.objectstyle.wolips.eomodeler.core.ActivatorResources 4 4 2015-04-29
> 21:13:07.546
> !MESSAGE Could not create SQL generator factory from configuration element:
> org.eclipse.core.internal.registry.ConfigurationE
org.objectstyle.wolips.eomodeler.core.ActivatorResources 4 4 2015-04-29
21:13:07.546
!MESSAGE Could not create SQL generator factory from configuration element:
org.eclipse.core.internal.registry.ConfigurationElementHandle@7b77
!STACK 1
org.eclipse.core.runtime.CoreException: Plug-in
org.objectstyle.wolips.eomodeler.eclipse was unable to load
I am having the same problem. Anyone getting closer to a solution?
Ken
> On Apr 29, 2015, at 7:55 AM, David Avendasora
> wrote:
>
>>
>> On Apr 29, 2015, at 4:07 AM, Hugi Thordarson > <mailto:h...@karlmenn.is>> wrote:
>>
>> I get this same e
> On Apr 29, 2015, at 4:07 AM, Hugi Thordarson wrote:
>
> I get this same error whenever attempting to generate SQL from Modeler.
> Happened after upgrading to WOLips from the new 4.4 repository, returning to
> my previous configuration (self compiled WOLips plugin) still work
I get this same error whenever attempting to generate SQL from Modeler.
Happened after upgrading to WOLips from the new 4.4 repository, returning to my
previous configuration (self compiled WOLips plugin) still works fine.
Cheers,
- hugi
// Hugi Thordarson
// http://www.loftfar.is/ <h
Hi all,
I’ve setup FrontBase as my development database server and am using Eclipse
4.4.2 and WOLips 4.4. When I try to generate SQL or reverse engineer a database
I get the following exception:
java.lang.ClassCastException:
org.objectstyle.wolips.eomodeler.core.sql.EOFSQLGeneratorFactory
;t been able to log SQL whatever
setting I used. Eventually I had to resort to code, and for me, this line
NSLog.allowDebugLoggingForGroups(NSLog.DebugGroupSQLGeneration|NSLog.DebugGroupDatabaseAccess|NSLog.DebugGroupEnterpriseObjects)
makes the SQL log to appear all right.
Regret to say
Hola!
With Wonder you want to do these:
# Enable delegate to emit SQL debugging info. The Logger used is
log4j.category.er.extensions.ERXAdaptorChannelDelegate.sqlLogging=DEBUG
# put this to true if you want to log sql stuff
er.extensions.ERXAdaptorChannelDelegate.enabled=true
# How long a
I have googled, searched the wiki, and tried everything I could think of, but I
can not get my sql to log. In my properties:
# ERExtensions
# Transaction - Switching this to debug will start the sql ouputting.
log4j.logger.er.transaction.adaptor.EOAdaptorDebugEnabled=DEBUG
still no SQL :-(
I
) and projects depending on UTF-8
Texts...
Am 25.11.2014 um 22:20 schrieb Chuck Hill :
> On 2014-11-25, 1:12 PM, "Ress, David A" wrote:
>
> Good afternoon,
>
> My current question is a development issue: I am using SQL Server and I
> cannot seem to find its plugin f
On 2014-11-25, 1:12 PM, "Ress, David A" wrote:
Good afternoon,
My current question is a development issue: I am using SQL Server and I cannot
seem to find its plugin framework within the latest Wonder builds listed at
https://github.com/wocommunity/wonder. Could someone please tell
Good afternoon,
My current question is a development issue: I am using SQL Server and I cannot
seem to find its plugin framework within the latest Wonder builds listed at
https://github.com/wocommunity/wonder. Could someone please tell me where I
can find it?
Without the plugin, I am getting
Hi Thomas,
look at ERXJDBCUtilities and ERXEOAccessUtilities for plenty of methods like:
ERXJDBCUtilities.executeUpdate(EOAdaptorChannel channel, String sql)
ERXEOAccessUtilities.evaluateSQLWithEntity(EOEditingContext ec, EOEntity
entity, String sql)
There should be something suiting your
Hi, what would be the best way to query in SQL these days in Project Wonder
?
I would like to use SQL directly sometimes for complex queries including
calculations (averages, medians..). Some of the previous solutions are
deprecated. Thanks in advance
gin is in build path:
The error just came up after I setup my new workstation, everything
else is working fine except Entity Modeler - Generate SQL
Troy
On 9/20/14 8:40 PM, Paul Yu wrote:
Troy
This sounds like a build path issue. Either the MySQL plugin is not
in you build path or some ot
e is
> working fine except Entity Modeler - Generate SQL
>
> Troy
>
>> On 9/20/14 8:40 PM, Paul Yu wrote:
>> Troy
>>
>> This sounds like a build path issue. Either the MySQL plugin is not in you
>> build path or some other MySQL related classpath iss
Hello Paul, nope MySQLPlugin is in build path:
The error just came up after I setup my new workstation, everything else
is working fine except Entity Modeler - Generate SQL
Troy
On 9/20/14 8:40 PM, Paul Yu wrote:
Troy
This sounds like a build path issue. Either the MySQL plugin is not
in
ncountered this error in Entity Modeler -
> SQL Generation.
> Here is the stacktrace:
>
> java.lang.IllegalStateException: Unable to load JDBCPlugIn 'MySQLPlugIn' for
> JDBCAdaptor@1036753793. Check your connection dictionary and make sure the
> specified JDBCPlu
Hello Everyone,
Just wondering if anyone have ever encountered this error in Entity
Modeler - SQL Generation.
Here is the stacktrace:
java.lang.IllegalStateException: Unable to load JDBCPlugIn 'MySQLPlugIn'
for JDBCAdaptor@1036753793. Check your connection dictionary and make
issue with the ERXEnterpriseObjectCache
causing the SQL generation to fail, but that issue needed to be fixed anyway as
it was, in fact, broken - a problem waiting to happen - even if SQL Generation
shouldn’t have cared.
Dave
On Apr 24, 2014, at 12:31 PM, David Avendasora
wrote:
>>
1 - 100 of 773 matches
Mail list logo
