Databases

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
  • Help required with Timestamp field

    7 answers - 326 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg Add To My Reddit

    Greetings,
    As we know the timestamp field is always updated by
    the DB engine with its value in hex format.
    I just want to know is there any way to export these timestamp values
    into flat files in their numeric form as with years, months, dates etc?
    Any help will be appreciated
    TIA
  • No.1 | | 503 bytes | |

    pankaj_wolfhunter@yahoo.co.in wrote:
    Greetings,
    As we know the timestamp field is always updated by
    the DB engine with its value in hex format.
    I just want to know is there any way to export these timestamp values
    into flat files in their numeric form as with years, months, dates etc?

    Any help will be appreciated

    TIA

    the timestamp datatype has nothing to do with date or time, it's a
    sequence number, so exporting it doesn't make any sence.

    joop
  • No.2 | | 296 bytes | |

    Thank for the reply.
    I didnt get it, if its just a sequence of numbers and that too in hex
    form,
    why do we have it. i mean if we cant export this, doesnt that mean that
    that we are loosing out that information, which is as good as not
    having only.
    TIA
  • No.3 | | 928 bytes | |

    pankaj_wolfhunter@yahoo.co.in wrote:
    Thank for the reply.
    I didnt get it, if its just a sequence of numbers and that too in hex
    form,
    why do we have it. i mean if we cant export this, doesnt that mean that

    that we are loosing out that information, which is as good as not
    having only.

    TIA

    ASE is using the timestamp internally to track changes to datapages for
    recovery purposis.
    You can basically use it if you want to implement optimistic locking and
    such things.
    As an example, if you have a web page where people can chenge data.
    You retrieve the record and it's timestamp, and release the lock on that
    page.
    Then the user changes the info.
    writeback of the data you check if the timestamp has changed or not.
    If it has changed then the record was changed in the meantime, if it
    hasn't chenged it's save to writeback the new info.

    joop
  • No.4 | | 214 bytes | |

    Thanks again.
    So does that mean if someone has timestamp field also, just in case,
    it cannot or should not be migrated as such.
    i mean if its ok to loose out with that informtion?
    TIA
  • No.5 | | 371 bytes | |

    pankaj_wolfhunter@yahoo.co.in wrote:
    Thanks again.
    So does that mean if someone has timestamp field also, just in case,
    it cannot or should not be migrated as such.
    i mean if its ok to loose out with that informtion?
    TIA

    Every ASE db has it's own timestamp range which is under control of the
    ASE and can not be updated manually.

    joop
  • No.6 | | 48 bytes | |

    Thanks for your time species.
  • No.7 | | 507 bytes | |

    In article <1134111767.360209.78290@z14g2000cwz.googlegroups.c om>,
    pankaj_wolfhunter@yahoo.co.in says
    Greetings,
    As we know the timestamp field is always updated by
    the DB engine with its value in hex format.
    I just want to know is there any way to export these timestamp values
    into flat files in their numeric form as with years, months, dates etc?

    Any help will be appreciated

    What Sybase version? The answer to this question varies dramatically
    from ASE to ASA.

Re: Help required with Timestamp field


max 4000 letters.
Your nickname that display:
In order to stop the spam: 6 + 5 =
QUESTION ON "Databases"

EMSDN.COM