Serial number format


#1

Hi,

Software:
We use Request Tracker version 1.0.7 in test
(we want to start ASAP productive)
and update, later, after the release to 2.0x.
OS:
RH7

maybe and hopefully a really simple question
(but I didn’t found in the Manual/FAQ):

How can I change (set) the format of serial number.
The unique identifier has a format 1 to xxx.

I prefer the format:
date-num [num daily started from 1] eg.
20010117-1 => yyyymmdd-num

Is this possible?

Thank you in advance
regards
Christian

-> Congratulation for this great Software !!


#2

We depend on the database to generate those unique serial numbers.
If you can get mysql to generate sequence numbers in the apropriate range,
it should just work. If you can’t make mysql do it, there’s not really any way.

One way (assuming that the serial #'s INT type has enough bits…which I can’t
look at right now) is to have a cron job that inserts an entry into the
each_req table with a serial number of yyyymmdd0000. As long as you never
get more than 9999 tickets in a given day this should be fine. Note that
I don’t know if anyone who’s ever done this.

    -jOn Mon, Jan 22, 2001 at 10:28:14AM +0100, Christian Janssen wrote:

Hi,

Software:
We use Request Tracker version 1.0.7 in test
(we want to start ASAP productive)
and update, later, after the release to 2.0x.
OS:
RH7

maybe and hopefully a really simple question
(but I didn’t found in the Manual/FAQ):

How can I change (set) the format of serial number.
The unique identifier has a format 1 to xxx.

I prefer the format:
date-num [num daily started from 1] eg.
20010117-1 => yyyymmdd-num

Is this possible?

Thank you in advance
regards
Christian

-> Congratulation for this great Software !!


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

jesse reed vincent – root@eruditorum.orgjesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

Linux is like a Vorlon. It is incredibly powerful, gives terse,
cryptic answers and has a lot of things going on in the background.


#3

You won’t have enough bits… INT is 4 bytes, so you’d only get up to a bit over
2,000,000,000.

Jesse wrote:

We depend on the database to generate those unique serial numbers.
If you can get mysql to generate sequence numbers in the apropriate range,
it should just work. If you can’t make mysql do it, there’s not really any way.

One way (assuming that the serial #'s INT type has enough bits…which I can’t
look at right now) is to have a cron job that inserts an entry into the
each_req table with a serial number of yyyymmdd0000. As long as you never
get more than 9999 tickets in a given day this should be fine. Note that
I don’t know if anyone who’s ever done this.

Matt.


#4

Indeed. However, if one is going to be doing local customization,
changing serial_num to a BIGINT should get you plenty of breathing room.

-jOn Mon, Jan 22, 2001 at 09:13:30PM -0800, Matthew Horoschun wrote:

You won’t have enough bits… INT is 4 bytes, so you’d only get up to a bit over
2,000,000,000.

Jesse wrote:

We depend on the database to generate those unique serial numbers.
If you can get mysql to generate sequence numbers in the apropriate range,
it should just work. If you can’t make mysql do it, there’s not really any way.

One way (assuming that the serial #'s INT type has enough bits…which I can’t
look at right now) is to have a cron job that inserts an entry into the
each_req table with a serial number of yyyymmdd0000. As long as you never
get more than 9999 tickets in a given day this should be fine. Note that
I don’t know if anyone who’s ever done this.

Matt.

jesse reed vincent – root@eruditorum.orgjesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

<Dr_Memory> the point is that words were exchanged. neurolinguistic
programming will do the rest. they should be showing up at my house
any day now.