Maybe I’m missing the point but why notLOAD table FROM filename USI
columnListHereJust make sure to exclude computed/autonum and any new columns.
This is an automated process involving hundreds of tables from multiple
instances of the database which have been modified in unknown ways. I have
tooling that creates the data dump and loads it into new instances of the
database but don't want to have to puzzle out the structural differences of
each source file.--Larry
On Saturday, August 12, 2017 9:15 PM, Buddy Walker
<[email protected]> wrote:
#yiv8157973230 #yiv8157973230 -- _filtered #yiv8157973230 {panose-1:2 4 5 3 5
4 6 3 2 4;} _filtered #yiv8157973230 {font-family:Calibri;panose-1:2 15 5 2 2 2
4 3 2 4;} _filtered #yiv8157973230 {font-family:Garamond;panose-1:2 2 4 4 3 3 1
1 8 3;}#yiv8157973230 #yiv8157973230 p.yiv8157973230MsoNormal, #yiv8157973230
li.yiv8157973230MsoNormal, #yiv8157973230 div.yiv8157973230MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:11.0pt;}#yiv8157973230 a:link,
#yiv8157973230 span.yiv8157973230MsoHyperlink
{color:blue;text-decoration:underline;}#yiv8157973230 a:visited, #yiv8157973230
span.yiv8157973230MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv8157973230
p.yiv8157973230msonormal0, #yiv8157973230 li.yiv8157973230msonormal0,
#yiv8157973230 div.yiv8157973230msonormal0
{margin-right:0in;margin-left:0in;font-size:11.0pt;}#yiv8157973230
span.yiv8157973230EmailStyle19 {color:windowtext;}#yiv8157973230
.yiv8157973230MsoChpDefault {font-size:10.0pt;} _filtered #yiv8157973230
{margin:1.0in 1.0in 1.0in 1.0in;}#yiv8157973230 div.yiv8157973230WordSection1
{}#yiv8157973230 _filtered #yiv8157973230 {}#yiv8157973230 ol
{margin-bottom:0in;}#yiv8157973230 ul {margin-bottom:0in;}#yiv8157973230 Larry
Maybe I’m missing the point but why not LOAD table FROM filename USI
columnListHere Just make sure to exclude computed/autonum and any new
columns. Buddy From: 'Lawrence Lustig' via RBASE-L
[mailto:[email protected]]
Sent: Saturday, August 12, 2017 12:26 PM
To: [email protected]
Subject: [RBASE-L] - Default to FILL for UNLOAD DATA I'm trying to migrate a
database which involves doing UNLOAD DATA from the load database and running
the resulting files into a new database. In some tables, the new database
tables have a few fields added at the end of the table. R:Base is refusing to
load these tables because, when the unloaded files are created, they do not
include the FILL statement to populate "extra" columns on the LOAD. Is there a
way to either:
- Tell R:Base to include FILL in the UNLOAD DATA command OR
- Tell R:Base that, when processing a LOAD command, if neither FILL or
NOFILL is specified the default should be FILL instead of NOFILL?
--Larry --
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
