• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: EOModeler : NSTimestamp - Factory Method / Conversion Method
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EOModeler : NSTimestamp - Factory Method / Conversion Method


  • Subject: Re: EOModeler : NSTimestamp - Factory Method / Conversion Method
  • From: lists <email@hidden>
  • Date: Tue, 2 Sep 2003 21:12:57 +0200

Am Dienstag, 02.09.03, um 20:57 Uhr (Europe/Berlin) schrieb Jonathan Rochkind:

Hm, I've never had that problem. Do you have the internal type of the attribute set to "Date"? You probably should. It sounds like you have it set to "Custom" with a class name of "NSTimestamp" instead---and the factory method and conversion method are blank. A custom internal type shouldn't be neccesary---"Date" should work fine.
first of all thank you for your quick reply.

yes, you're right, my internal datatype is 'custom' and the class attribute of the internal datatype is 'NSTimestamp'. I changed it from date to that setting because my database records that i created with 'date' contained nothing but the date, but not the times. so i assumed that the date setting does what it says: it stores the date, while a timestamp contains more information. I might be wrong, and the reason for the times disappearing using 'date' lies somewhere else.

so with this setting i'm getting the results that i want but EOModeler is complaining. Being a newbie it renders me uncertain. i assume, i'm doing something wrong, when a warning appears. that's why i'm asking.




There's probably a way to get 'Custom' to work, but I don't know what it is. On the other hand, if everything IS working, maybe you've already found the way to get it to work, it's just confusing EOModeler. There are worse things than confusing EOModeler, as long as everything still works at deployment. But internal type of 'Date' is probably the way to go.


--Jonathan

At 08:35 PM 9/2/2003 +0200, you wrote:
Hello list,

i'm just starting to program WO and i'm really exited. Here's something that the Docs didn't cover: I'm Using NSTimestamps on the WOApp-side and DATETIME on the database-side to model my creation and modification dates of my records (rows) in my database. Actually storing and retrieving data works fine, but:

EOModeler complains when saving the model that Factory and Conversion Methods of my datestoring rows are undefined (which is true). I don't know what to enter in order to make it stop complaining.

can somebody explain?

thank you very much
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: EOModeler : NSTimestamp - Factory Method / Conversion Method
      • From: Jonathan Rochkind <email@hidden>
  • Prev by Date: Re: EOModeler : NSTimestamp - Factory Method / Conversion Method
  • Next by Date: Re: EOModeler : NSTimestamp - Factory Method / Conversion Method
  • Previous by thread: Re: EOModeler : NSTimestamp - Factory Method / Conversion Method
  • Next by thread: Re: EOModeler : NSTimestamp - Factory Method / Conversion Method
  • Index(es):
    • Date
    • Thread