Re: FoxPro Vs. PostgreSQL

From: "Florian Reiser" <florian(dot)reiser(at)ra-bc(dot)de>
To: <aspire420(at)hotpop(dot)com>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: FoxPro Vs. PostgreSQL
Date: 2003-12-15 07:55:58
Message-ID: 001a01c3c2e0$e093a0a0$6ac9280a@domw2k.int
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general

Hello Kashyap,

the limitations of VFP8 (the newest FoxPro version are the following
(according to the VFP8 manual):

Some capacities may be limited by available memory.

Category Feature Capacity

Table and Index Files

Maximum # of records per table file 1 billion
Maximum size of a table file 2 gigabytes
Maximum size of an FPT file 2 gigabytes
Maximum # of characters per record 65,500
Maximum # of fields per record1 255
Maximum # of tables open at one time2 65,535
Maximum # of characters per table field 254
Maximum # of bytes per index key in a non-compact index3 100
Maximum # of bytes per index key in a compact index3 240
Maximum # of open index files per table2 Unlimited
Maximum # of open indexes in all work areas2 Unlimited
Maximum # of relations Unlimited
Maximum length of relational expressions Unlimited

Field Characteristics

Maximum size of character fields 254
Maximum size of numeric and float fields 20
Maximum number of characters in field names in a free table 10
Maximum number of characters in field names for a table contained in a
database 128
Minimum value of an integer -2,147,483,647
Maximum value of an integer 2,147,483,647
Digits of precision in numeric computations. Visual FoxPro can handle
numbers up to 9007199254740992 (2^53) in exact computations. 16
Miscellaenous:
64 bits = 8 bytes
Largest number = 10 ^ 308 = 2 ^ 1023
-> 10 bits per exponent + 1 for exponent sign plus 1 for number sign => 12
bits
Leaving 52 bits for the mantissa + 1 for implied normalized bit -> 53 bits
LOG10(2^53) = 15.95 decimal digits accuracy

Variables and Arrays

Default # of variables 1,024
Maximum # of variables 65,000
Maximum # of arrays 65,000
Maximum # of elements per array 65,000

Program and Procedure Files

Maximum # of lines in source program files Unlimited
Maximum size of compiled program
modules4 64K
Maximum # of procedures per file Unlimited
Maximum # of nested DO calls 128
Maximum # of READ nesting levels 5
Maximum # of nested structured programming commands 384
Maximum # of passed parameters 26
Maximum # of transactions 5

Report Designer Capacities

Maximum # of objects in a report definition2 Unlimited
Maximum length of a report definition 20 inches
Maximum # of grouping levels 128
Maximum length of character report variables 255

Other Capacities

Maximum # of open windows (all types)2 Unlimited
Maximum # of open Browse windows 255
Maximum # of characters per character string or memory variable 16,777,184

Maximum # of characters per command line 8,192
Maximum # of characters per label control on a report 252
Maximum # of characters per macro substituted line 8,192
Maximum # of open files System limit
Maximum keystrokes in keyboard macro 1,024
Maximum fields that can be selected by a SQL SELECT statement 255
Maximum length of a string literal 255
Maximum # of pages in a report at runtime 32767

1 If one or more fields allow null values, the limit is reduced by one to
254 fields.
2 Limited by memory and available file handles. .cdx files use only one file
handle.
3 If the collating sequence is set to MACHINE, each character uses one byte.
If the collating sequence is not set to MACHINE, each character uses two
bytes. If the indexed field supports null values, one additional byte is
used in the index key. Note that non-machine indexes are always compact.
4 A program module is one procedure. A program or application can contain an
unlimited number of program modules.

Regards
Florian Reiser

-----Original Message-----
From: pgsql-general-owner(at)postgresql(dot)org
[mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Sai Hertz And
Control Systems
Sent: Sunday, December 14, 2003 4:19 PM
To: pgsql-general(at)postgresql(dot)org
Cc: Postgres Admin List
Subject: [GENERAL] FoxPro Vs. PostgreSQL

Hello all ,

I am a OpenSource S/W developer and my clients are from remote part of
Himachal Pradesh India.
I am providing my clients,
software
Build on PostgreSQL 7.3.x as backed
and yes , they (clients) ought to save a lot while using my software as
it runs on Linux
But theirs one Prick Our Competitor he is providing solution in what else
FoxPro + Win98
and this competitor justifies his software as Superior because some of
the Indian local banks use this
clumsy set of tool to manage their bureaucratic banking work system.

What I want is some support from this good community to give me some
1. Tips
2. Links
3. Advise
for FoxPro and its limits (As could be told to a layman)
as how to crush my competitor for M$ tools,
Its time to prove The M$ Guys that they have $$$$$ Power and we the GNU
people have a
social perspective of doing work.

Would be greatefull for all your Comments / Bashing and yes Support

Please..........................

To Add More :
My Clients are Agriculture Banks and cannot afford the M$ tools. and yes
all the Win98 installation on their computers are
pirated.

Regards,
V Kashyap

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Ganesan Kanavathy 2003-12-15 08:46:30 Shutdown pg db
Previous Message pginfo 2003-12-15 06:05:09 Re: [ADMIN] FoxPro Vs. PostgreSQL

Browse pgsql-general by date

  From Date Subject
Next Message Tino Wildenhain 2003-12-15 08:30:03 Re: 7.5 features
Previous Message pginfo 2003-12-15 06:05:09 Re: [ADMIN] FoxPro Vs. PostgreSQL