Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Development #71

Merged
merged 121 commits into from
Jun 12, 2020
Merged

Development #71

merged 121 commits into from
Jun 12, 2020

Conversation

allanbowe
Copy link
Contributor

Release for Version 1 of the adapter. This uses the file upload mechanism, which is orders of magnitude faster than using macro variables for sending data to SAS. It also now uses proc json to return data to SAS, alternatively it will use the old method if the SAS installation is lower than 9.4.

Note the new syntax for obtaining tables:

%bafgetdatasets() - this will convert ALL input files to SAS datasets (no longer need one call per dataset)

And for sending tables back to the frontend:

%bafheader()
    %bafOutDataset(jsObjName, work, sasDatasetName)
%bafFooter()

On the javascript side there is a new function for creating data:

var myData=new h54s.SasData([{col1: "some_string, col2: 1}],'forSAS')

rawfocus and others added 30 commits December 16, 2015 10:36
 * Use of proc contents instead of dictionary tables
 * Use of datastep to create macvars negates the need for noprint option on SQL (the remaining proc SQL does not send to print output).  Also, no  * longer limited to 999 columns.
replaced ```format _all_;``` with ```format _numeric_ best32.;``` to gain maximum precision for numerics.  Note that character formats are no longer stripped.   Could not think of a use case for this..  But to re-enable stripping of character formats, just add another line (```format _character_;```)
adding %else for efficiency
removing redundant code
need to retain variable order to preserve downstream logic in customer app
fix to avoid conflict with reserved USER variable in proc sql approach.  Fixes #27.
reverting to SQL view (datastep view caused 'could not parse json' issue on client side)
@allanbowe
Copy link
Contributor Author

dist has been rebuilt, all conflicts resolved, tests are passing - should be good to go (has updated README also)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants