I've been attempting to port applications from Pervasive SQL to PG.
Pervasive is interesting because it runs on top of btrieve. This allow
legacy apps
and SQL systems to co-exist. It's quirky and buggy, but it's better than PG
because it can do the following.
1. Have more than 7 fields on a btree index
2. There exists a table called inmaster it has a char(20) field called
stock_code.
pervasive can create a view (product) that splits the consituent characters
into fields.
PG cannot handle this. see below.
create view product as
Select code As Stock_Code,
Substr(Code,1,1) As Process_ID,
Substr(Code,2,2) As SubProcess_ID,
Substr(Code,4,1) As SubStrate_ID,
Substr(Code,5,2) As Length_ID,
Substr(Code,7,2) As Width_ID,
Substr(Code,9,2) As Thickness_ID,
Substr(Code,11,3) As Face_ID,
Substr(Code,14,1) As Facefinish_ID,
Substr(Code,15,3) As Back_ID
-- Substr(Code,18,1) As Backfinish_ID
From INMASTER;
ERROR: DefineQueryRewrite: rule plan string too big.
This should not occur. Would someone please pick it up and put it on the
TODO list.
Regards
John
