Subject | Re: [firebird-support] Who's using some GUID (Global Unique IDentifiers) in FB? |
---|---|
Author | David Johnson |
Post date | 2004-04-08T06:04:38Z |
On a 100,000 row table your lookup will average 2 I/O with either GUID or INT. 4,000,000 rows is where you will start to see a difference. The GUID will go to 4 I/O (40ms) per row while the INT is still doing 3 I/O (30ms) per row.
The larger your table, the more efficient the INT will be in comparison.
The larger your table, the more efficient the INT will be in comparison.
----- Original Message -----
From: Rafael Szuminski
To: firebird-support@yahoogroups.com
Sent: Wednesday, April 07, 2004 8:28 AM
Subject: Re: [firebird-support] Who's using some GUID (Global Unique IDentifiers) in FB?
> Can you advise me about "Global Unique IDentifiers", which Udf to use
> and is it really efficient ?
I am using GUIDs as PK and FK in multiple apps. My GUIDs are generated on the
client side and are stored in char(32) fields. Performance wise I could not
measure any difference vs INT PK on a table with 100.000 rows.
> I want ot use it in order to do disconnected works with data and
> after update database.
> It would be nice if you have a little exemple.
What development environment are you using?
Raf
akestion wrote:
> Hello,
>
> Can you advise me about "Global Unique IDentifiers", which Udf to use
> and is it really efficient ?
> I want ot use it in order to do disconnected works with data and
> after update database.
> It would be nice if you have a little exemple.
> Thanks you.
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
--
Rafael Szuminski
Email:raf@...
Phone:(949)939 - 2458
www.BDCSoftware.com
Yahoo! Groups Sponsor
ADVERTISEMENT
------------------------------------------------------------------------------
Yahoo! Groups Links
a.. To visit your group on the web, go to:
http://groups.yahoo.com/group/firebird-support/
b.. To unsubscribe from this group, send an email to:
firebird-support-unsubscribe@yahoogroups.com
c.. Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]