Bacula-users

Re: [Bacula-users] getting rid of the base64 encoded lstat field - table size testing

2009-04-15 14:44:32
Subject: Re: [Bacula-users] getting rid of the base64 encoded lstat field - table size testing
From: Martin Simmons <martin AT lispworks DOT com>
To: bacula-users AT lists.sourceforge DOT net
Date: Wed, 15 Apr 2009 19:36:22 +0100
>>>>> On Wed, 15 Apr 2009 11:58:08 +0800, Craig Ringer said:
> 
> Anyway, the expanded schema:
> 
> CREATE TABLE file2 (
>     fileid bigint,
>     fileindex integer,
>     jobid integer,
>     pathid integer,
>     filenameid integer,
>     markid integer,
>     st_dev integer,
>     st_ino integer,
>     st_mod integer,
>     st_nlink integer,
>     st_uid integer,
>     st_gid integer,
>     st_rdev bigint,
>     st_size integer,
>     st_blksize integer,
>     st_blocks integer,
>     st_atime integer,
>     st_mtime integer,
>     st_ctime integer,
>     linkfi integer,
>     md5 text
> );

Thanks, I was wondering what you had done about integers.  Is integer a 32-bit
quantity?  Beware that many of these stat fields are 64-bit on modern systems
(even for 32-bit operating systems).

__Martin

------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users