I'm stuck and need help really quick please :-)
Could somebody please help explain why the following might occur.
Much appreciated...
with regards,
--
Lachlan Deck
2007-02-09 17:53:30,205 [WorkerThread2 ] ERROR
com.ish.webobjects.appserver.ISHApplication - Handling exception
java.lang.
Hi there,
For some time now we've been using the technique of defining a non-
class property in the model called "derivedCount" with it's
definition as count(*).
Works great. e.g.,
EOEditingContext ec; // assume exists
EOFetchSpecification fetchSpec; // assume exists
NSArray results;
fetch
Hello -
What is the rule to have all my dates displayed say, Feb 7, 2007 ??
thanks
James Cicenia
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Upda
Hi James,
1. I can't really help you with writing stored procedures other than
saying your procedure should be a function that returns a ref_cursor
if you are expecting multiple results.
2. You can fetch using :
public static NSArray rawRowsForStoredProcedureNamed(EOEditingContext
ec, Str
Grüß René;
Ok, my use case didn't need to handel numbers and booleans. But a
first test showed: the method didn't handle dates as well :-(
It was my understanding that property lists were not able to handle
dates or booleans or at least just moved those types around using
strings and one h
Maybe I'm missing something somewhere, but I can't seem to find the answer.
To optimize things, I'd like to do frequent fetches using Oracle stored
procedure. There are two parts to this:
1. How do I write the Oracle stored procedure in PL/SQL? What should be
returned? According to Tom Kyte, this
In case that can help you, here is more info on the RAM management in
the MacPro (which I believe is close to the XServe's) :
http://www.anandtech.com/mac/showdoc.aspx?i=2816&p=6
Fabrice
On Feb 8, 2007, at 2:48 AM, Karl Gretton wrote:
Well the Xserve obviously uses FB-DIMM..so it is serial in
2007/2/8, René Bock <[EMAIL PROTECTED]>:
Hi
On the first sight, NSPropertyListSerialization.dictionaryForString
ability to parse classic property lists and XML PropertyLists looked quite
promising for simple data exchange between applications.
Further readings of the developer docs yields:
"
Hi
On the first sight, NSPropertyListSerialization.dictionaryForString
ability to parse classic property lists and XML PropertyLists looked
quite promising for simple data exchange between applications.
Further readings of the developer docs yields:
"Some methods do not support XML proper
