GitLab

Add Function Library _YDBOCTOVISTAF

See merge request !11

CURR_TIMESTAMP() --horolog datetime  or CURR_TIMESTAMP("v") Fileman Datetime
DATEFORMAT(value,formatcode) -- formats based on datetime type returns MM/DD/YYYY HH:MM:SS as default
			     -- uses "5ZSP" for fileman dates unless formatcode is otherwise specified
			     -- if fileman date calls VA routine $$FMTE^XLFDT(value,format) to format
IFNULL(value,replacer)	    -- Takes a passed field and replaces a null value with whatever is passes as the second
				argument
TOKEN			    -- Renamer for Mumps $Piece function
Replace(value,finder,replacement) -- takes any string and searches for the finder string to replace it with the
				replacement string, modified string is returned
SUBSTRING(value,start,range)   -- returns a part of passed value staring at the position specified by
				start (2nd parameter), continuing for range (3rd parameter) or
				end of string whichever comes first
FMGET(file#,field# or name,keys) -- VistA specific, uses VA Routine $$GET1^DIQ to take foreign kets and fetch a field 					from the specified
LEFTY(value,characters)		-- return left x characters from value
RIGHTY(value,caharacters)	-- return right x charaters from value
PATINDEX(value,searchstring)	-- returns the position of the first occruence of search string in value
NUMBER(value)			-- returns the mumps equivalent of +value, numeric portion returned only

Change translations for date, timestamp and primary_key to numeric

See merge request !13

Octo previously treated INTEGER and NUMERIC as equivalent, however
recent changes have changed that equivalency and now the correct
data type needs to be specified.

In VistA dates and timestamps are numerics with a decimal point.
The primary key data type is also converted to a numeric as it is
possible to have decimals in the IEN columns.

[#4] Only put GLOBAL keyword when PIECE keyword is used

Closes #4

See merge request !12

The GLOBAL keyword is only useful when the PIECE keyword is used
and can be confusing when used with the EXTRACT keyword.

Set Y variable

See merge request YottaDB/DBMS/ydbvistaocto!10

Some computed expressions don't check to see if the Y variable is
set before accessing it. Set Y to the empty string (which appears
to work for computed expressions tested so far).

Escape primary key lines in CREATE TABLE statements

See merge request YottaDB/DBMS/ydbvistaocto!9

Add backticks to primary key columns that were missed in a previous
commit

Undo change to convert INTEGER to CHAR

See merge request YottaDB/DBMS/ydbvistaocto!8

It was mistakenly believed that the INTEGER data type didn't support
floating point numbers and needed to be a CHARACTER data type. Instead
what was necessary was a change to octo to allow casting as an INTEGER
data type to allow the correct comparisions to occur.

Add gitignore file

See merge request YottaDB/DBMS/ydbvistaocto!7

Change DATE/TIMESTAMP data types to character

See merge request YottaDB/DBMS/ydbvistaocto!6

Until Octo supports date/time map them to the character data type

[#1] Remove hard coded file "vista-new.sql" and escape table and column names

See merge request YottaDB/DBMS/ydbvistaocto!5

Add a new argument "PATH" to MAPALL and MAPONE to allow users to specify
the file name and path for the generated DDL.

Add backticks "`" to table and column names to escape any SQL/Octo reserved
words.

Remove debug computed expressions

See merge request YottaDB/DBMS/ydbvistaocto!4

Add REPLACE SQL function implementation

See merge request YottaDB/DBMS/ydbvistaocto!3

Initial implementation

See merge request YottaDB/DBMS/ydbvistaocto!2

# Conflicts:
#   _YDBOCTOVISTAM.m

Initial implementation

See merge request YottaDB/DBMS/ydbvistaocto!1

This maps VistA FileMan files into Octo tables.

This maps VistA FileMan files into Octo tables.