Web forum is in read-only mode. Login as active registered customer for write access
  Forum Search   New Posts New Posts

Aurelius Export does not create TDateTime anymore

 Post Reply Post Reply
Author
Ronald Janse View Drop Down
Senior Member
Senior Member
Avatar

Joined: 20 Aug 2015
Posts: 272
Post Options Post Options   Quote Ronald Janse Quote  Post ReplyReply Direct Link To This Post Topic: Aurelius Export does not create TDateTime anymore
    Posted: 27 Aug 2015 at 9:12am
I've updated and it looks ok now!
Back to Top
Wagner R. Landgraf View Drop Down
TMS Support
TMS Support
Avatar

Joined: 18 May 2010
Posts: 2494
Post Options Post Options   Quote Wagner R. Landgraf Quote  Post ReplyReply Direct Link To This Post Posted: 26 Aug 2015 at 11:55pm
Yes, it's a bug in TMS Data Modeler. Actually, it was. There is a new update available now which fixes this issue. Please use your automatic update to get the new version.
Back to Top
Ronald Janse View Drop Down
Senior Member
Senior Member
Avatar

Joined: 20 Aug 2015
Posts: 272
Post Options Post Options   Quote Ronald Janse Quote  Post ReplyReply Direct Link To This Post Posted: 26 Aug 2015 at 3:14pm
The image I inserted in the post does not work.
It sows a page in the Data modeler of Table defitemiveaus. The fields tab says:

Field name   Datatype
..
datumvan     Timestamp
datumtm       Timestamp
Back to Top
Ronald Janse View Drop Down
Senior Member
Senior Member
Avatar

Joined: 20 Aug 2015
Posts: 272
Post Options Post Options   Quote Ronald Janse Quote  Post ReplyReply Direct Link To This Post Posted: 26 Aug 2015 at 3:10pm
I have a Table, that is declared like this:

The Aurelius Export used to export the last two fields like this:

   [Column('datumvan', [])]
    Fdatumvan: Nullable<TDateTime>;
   
    [Column('datumtm', [])]
    Fdatumtm: Nullable<TDateTime>;

   
Which is the way I want it and I expect it to be.
But suddenly I get this:

    [Column('datumvan', [])]
    Fdatumvan: Nullable<double>;
   
    [Column('datumtm', [])]
    Fdatumtm: Nullable<double>;

   
If I generate a PostgreSQL script, I get a correct script for the database:

CREATE TABLE defitemniveaus (
  itemniveauid INTEGER NOT NULL DEFAULT nextval('defitemniv_itemnivid_seq'::regclass),
  importid BIGINT,
  parent INTEGER,
  code CHAR(30),
  omschrijving VARCHAR(100),
  afbeeldingid INTEGER,
  datumvan TIMESTAMP,
  datumtm TIMESTAMP,
  CONSTRAINT defitemniv_pkey PRIMARY KEY (itemniveauid)
);


 So whats wrong? A bug in Aurelius?
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down