Many to many relation. How?

[End If Software - Ralf Sander]

on 07.12.2004 8:49 Uhr, Ruslan Zasukhin wrote:

> On 12/7/04 6:20 AM, "Robert Brenstein" <rjb at rz.uni-potsdam.de> wrote:
> 
>>> Hm, not bad. But won't a much longer string decrease speed of queries?
>>> The best solution would be an integer, wouldn't it? But then the
>>> database could run out anytime.
>>> Or do you think of a relation based on more than 2 fields?
>>> 
>>> 
>>> Cheers,
>>> Ralf
>> 
>> RecId is an integer. So is (at least can be) the timestamp. I would
>> not be concerned about the speed decrease related to having a tad
>> longer query string. The network performance will remain the
>> bottleneck IMHO.
> 
> That is right.
> 
> Also note that TIMESTAMP can be made as ULONG or ULLONG (8 byte) integer
> value in the format
> 
> YYYYMMDD  HHMMSS

OK, let's see, if I got it.

I take the current date and time as string and add the recid as string and
store it into a LLong

val("20041205143211"  + str(recid))
And this is really save? Or must the recid filled up with "0" s?

val("20041205143211"  + "00000000000125")

sorry, may be silly, but I and math....

Thanks,
Ralf