On Tue, Dec 21, 2004 at 17:50:06 -0500,
"Frank D. Engel, Jr." <[EMAIL PROTECTED]> wrote:
>
> Also, given the amount of data you are talking about, and assuming that
> you are inserting all of this data in one big lump, you may wish to
> VACUUM FULL after doing your INSERTs (not after each one,
On Wed, Dec 22, 2004 at 01:24:57 +,
"Vladimir S. Petukhov" <[EMAIL PROTECTED]> wrote:
> Yes, of course, this is example only.
> But relation between tables is not important now...
It is important for design. You should use a normallized design initially
and consider denormalized designs if y
I absolutly agree with you, thank.
On Tuesday 21 December 2004 22:50, you wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Why would it be?
>
> The only real advantage to what you are suggesting would be slightly
> reduced disk space usage, and just maybe *very* slightly improved
> per
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Why would it be?
The only real advantage to what you are suggesting would be slightly
reduced disk space usage, and just maybe *very* slightly improved
performance on low-memory servers, or servers with very slow disks, but
I find it unlikely that th
On Tuesday 21 December 2004 22:00, Bruno Wolff III wrote:
> On Wed, Dec 22, 2004 at 00:16:06 +,
>
> "Vladimir S. Petukhov" <[EMAIL PROTECTED]> wrote:
> > On Tuesday 21 December 2004 21:21, Bruno Wolff III wrote:
> > > On Tue, Dec 21, 2004 at 20:47:31 +,
> > >
> > > "Vladimir S. Petukhov
On Wed, Dec 22, 2004 at 00:16:06 +,
"Vladimir S. Petukhov" <[EMAIL PROTECTED]> wrote:
> On Tuesday 21 December 2004 21:21, Bruno Wolff III wrote:
> > On Tue, Dec 21, 2004 at 20:47:31 +,
> >
> > "Vladimir S. Petukhov" <[EMAIL PROTECTED]> wrote:
> > > Ok, this is a real example:
> > >
> >
On Tuesday 21 December 2004 21:21, Bruno Wolff III wrote:
> On Tue, Dec 21, 2004 at 20:47:31 +,
>
> "Vladimir S. Petukhov" <[EMAIL PROTECTED]> wrote:
> > Ok, this is a real example:
> >
> > CREATE TABLE account (
> > val1 BIGINT NULL,
> > val2BIGINT NULL,
> > ...
> >
>
On Tue, Dec 21, 2004 at 20:47:31 +,
"Vladimir S. Petukhov" <[EMAIL PROTECTED]> wrote:
> Ok, this is a real example:
>
> CREATE TABLE account (
> val1 BIGINT NULL,
> val2BIGINT NULL,
> ...
>
> dayposSMALLINTNULL, -- Day position
> hourpos SMALLINTNU
Instead of having separate fields for day, hour, ... - why not use
timestamp values?
On Dec 21, 2004, at 3:47 PM, Vladimir S. Petukhov wrote:
Ok, this is a real example:
CREATE TABLE account (
val1 BIGINT NULL,
val2BIGINT NULL,
...
dayposSMALLINTNULL, -- Day pos
Ok, this is a real example:
CREATE TABLE account (
val1 BIGINT NULL,
val2BIGINT NULL,
...
dayposSMALLINTNULL, -- Day position
hourpos SMALLINTNULL, -- Hour position
idINT NULL -- Link to the object
);
On Tuesday 21 December 2004 1
On Mon, Dec 20, 2004 at 12:13:31 +,
"Vladimir S. Petukhov" <[EMAIL PROTECTED]> wrote:
> Hi
> Sorry for my English..
>
> I need to organize database structure for saving statistic data for objects.
> I
> have about 24 * 31 * 4 fields (4 month, 31 days, 24 hours) of data for one
> object.
11 matches
Mail list logo