ay the way you're wanting it to.
>>
>> Of course since I don't know C, by doing that I have no clue what else I
>> might just have broken which relied on the old format, but hey :)
>>
>>
>> -Original Message-
>> From: sqlite-users [mailto:sqlite-users-boun...@ma
On Oct 14, 2016, at 1:27 PM, Don V Nielsen wrote:
>
> I can read C, but I don't know how to compile it.
https://www.sqlite.org/howtocompile.html
Once you get SQLite to build, make the suggested change and say “make” again.
The sqlite3 program will be rebuilt, since make knows that sqlite3 dep
e similar to:
> >
> > CREATE VIRTUAL TABLE mainframe_file USING mainframe ( '',
> > '', []); --> open filename, prepare to write in
> > specified format, write header
> > INSERT INTO mainframe_file SELECT ...; -> stuff in data, write record
> >
..@mailinglists.sqlite.org] On
Behalf Of Don V Nielsen
Sent: Friday, October 14, 2016 7:39 AM
To: SQLite mailing list
Subject: Re: [sqlite] .mode column .width .separator
Thank you, Gunter. I will investigate virtual tables; it's a bit over my
head at the moment.
My final implementation was
> Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org]
> Im Auftrag von Don V Nielsen
> Gesendet: Donnerstag, 13. Oktober 2016 20:51
> An: General Discussion of SQLite Database sqlite.org>
> Betreff: [sqlite] .mode column .width .separator
>
> I am usin
Discussion of SQLite Database
Betreff: [sqlite] .mode column .width .separator
I am using the command line shell SQLite 3.14.2 2016-09-12. I'm working with
mainframe data in a fixed format.
I would like to use .mode column to create my output text file in a fixed
layout. I set all my column w
Thanks John. I had a feeling you would have encountered this sort of stuff.
And thanks for your time, Simon.
All is appreciated.
And thanks in advance, Dr. Hipp, if you act on this...allowing a \0 row
separator in column mode. It would simplify the life of us mainframers.
dvn
On Thu, Oct 13,
On Thu, Oct 13, 2016 at 2:42 PM, Don V Nielsen
wrote:
> Thanks, but it appears that ".mode column" triggers it, and .separator does
> not appear to have any influence in that mode.
>
> Out of curiosity, it appears that the row separator (in windows) is a
> single character. Do you know to specify
Thanks, but it appears that ".mode column" triggers it, and .separator does
not appear to have any influence in that mode.
Out of curiosity, it appears that the row separator (in windows) is a
single character. Do you know to specify as the row separator? Everything
I attempt is taken as literal
On 13 Oct 2016, at 7:51pm, Don V Nielsen wrote:
> The .separator command does not provide any
> mechanism for turning it off. Is there a way?
Can't try it now but does
.separator ""
do what you want ?
Simon.
___
sqlite-users mailing list
sqlite-use
I can do this, which works. But the redundancy bothers me, and is prone to
finger-check errors.
with pre_process as (
select
recid,
z_num,
zip,
zip4,
dpbc,
case when piecerate in ('AF','RF') and version_id = '81' then '81' else
segment end as segment,
... blah blah ...
These are simply blanks, 0x20, use to create separation of the output
columns. I'm assuming this is an inherent behavior for readability. If the
output was not being directed to the output file, it would be directed to
the display.
I'm trying to avoid pre processing (creating a table or view of th
On 13 Oct 2016, at 7:51pm, Don V Nielsen wrote:
> Unfortunately, there are two blanks separating each column
Can you tell what characters these are ? Perhaps use a hexdump facility.
My guess at this point is that you should continue with the file you have
already developed and then post-proc
I am using the command line shell SQLite 3.14.2 2016-09-12. I'm working
with mainframe data in a fixed format.
I would like to use .mode column to create my output text file in a fixed
layout. I set all my column widths using .width. I then output my data to a
file. Unfortunately, there are two bl
14 matches
Mail list logo
