![]() | |
#11
| |||
| |||
|
|
"Phil Carmody" <thefatphil_demunged (AT) yahoo (DOT) co.uk> wrote in message news:87abcoesl0.fsf (AT) nonospaz (DOT) fatphil.org... "Rob Nicholson" <rob.nicholson (AT) nospan (DOT) com> writes: Not sure if this is a good place to post, but we're trying to reverse engineer an Oracle database which has two fields for date & time. They don't seem to be encoded using the standard Oracle date/time fields so we suspect the developer has used some bespoke encoding system. So I thought it would be a good challenge for somebody mathematically minded. The example I currently have is: 17th October 2008 encoded as 131598865 Hexadecimal: 0x07D80A11 And: 07D8 = 2008 0A = 10 11 = 17 13:54:49 encoded as 221655296 Hexadecimal: 0x0D363100 And: 0D = 13 36 = 54 31 = 49 Which means it's simply byte byte word format. i.e., day + month << 8 + year << 16 |
#12
| |||
| |||
|
|
"Phil Carmody" <thefatphil_demunged (AT) yahoo (DOT) co.uk> wrote in message news:87abcoesl0.fsf (AT) nonospaz (DOT) fatphil.org... "Rob Nicholson" <rob.nicholson (AT) nospan (DOT) com> writes: Not sure if this is a good place to post, but we're trying to reverse engineer an Oracle database which has two fields for date & time. They don't seem to be encoded using the standard Oracle date/time fields so we suspect the developer has used some bespoke encoding system. So I thought it would be a good challenge for somebody mathematically minded. The example I currently have is: 17th October 2008 encoded as 131598865 Hexadecimal: 0x07D80A11 And: 07D8 = 2008 0A = 10 11 = 17 13:54:49 encoded as 221655296 Hexadecimal: 0x0D363100 And: 0D = 13 36 = 54 31 = 49 Which means it's simply byte byte word format. i.e., day + month << 8 + year << 16 |
#13
| |||
| |||
|
|
"Phil Carmody" <thefatphil_demunged (AT) yahoo (DOT) co.uk> wrote in message news:87abcoesl0.fsf (AT) nonospaz (DOT) fatphil.org... "Rob Nicholson" <rob.nicholson (AT) nospan (DOT) com> writes: Not sure if this is a good place to post, but we're trying to reverse engineer an Oracle database which has two fields for date & time. They don't seem to be encoded using the standard Oracle date/time fields so we suspect the developer has used some bespoke encoding system. So I thought it would be a good challenge for somebody mathematically minded. The example I currently have is: 17th October 2008 encoded as 131598865 Hexadecimal: 0x07D80A11 And: 07D8 = 2008 0A = 10 11 = 17 13:54:49 encoded as 221655296 Hexadecimal: 0x0D363100 And: 0D = 13 36 = 54 31 = 49 Which means it's simply byte byte word format. i.e., day + month << 8 + year << 16 |
#14
| |||
| |||
|
|
17th October 2008 encoded as 131598865 Hexadecimal: 0x07D80A11 And: 07D8 = 2008 0A = 10 11 = 17 |
#15
| |||
| |||
|
|
17th October 2008 encoded as 131598865 Hexadecimal: 0x07D80A11 And: 07D8 = 2008 0A = 10 11 = 17 |
#16
| |||
| |||
|
|
17th October 2008 encoded as 131598865 Hexadecimal: 0x07D80A11 And: 07D8 = 2008 0A = 10 11 = 17 |
#17
| |||
| |||
|
|
17th October 2008 encoded as 131598865 Hexadecimal: 0x07D80A11 And: 07D8 = 2008 0A = 10 11 = 17 |
#18
| |||
| |||
|
|
Ah! Thanks - can I buy you a virtual pint via PayPal? |
#19
| |||
| |||
|
|
Ah! Thanks - can I buy you a virtual pint via PayPal? |
#20
| |||
| |||
|
|
Ah! Thanks - can I buy you a virtual pint via PayPal? |
![]() |
| Thread Tools | |
| Display Modes | |
| |