Node.js Code Samples (SAP HANA) - Versionsgeschichte

Matt am 27. März 2022 um 18:03 Uhr

2022-03-27T18:03:23Z

← Nächstältere Version		Version vom 27. März 2022, 20:03 Uhr
Zeile 1:		Zeile 1:
	This entry contains SAP HANA specific server-side JavaScript listings for Node.js runtime within XS Advanced environment.		This entry contains SAP HANA specific server-side JavaScript listings for Node.js runtime within XS Advanced environment.

	For basics knowledge on JavaScript language itself see [[JavaScript ~~Basics~~]]		For basics knowledge on JavaScript language itself see [[JavaScript Linkliste]]

	== Language Basics on Node.js Runtime ==		== Language Basics on Node.js Runtime ==

2020-11-16T09:36:28Z

Language Basics on Node.js Runtime

← Nächstältere Version		Version vom 16. November 2020, 11:36 Uhr
Zeile 5:		Zeile 5:
	== Language Basics on Node.js Runtime ==		== Language Basics on Node.js Runtime ==

	https://github.com/mattxdev/~~openSAPHANA~~/blob/master/srv/router/routes/JavaScriptBasics.js		https://github.com/mattxdev/opensap-hana7/blob/master/srv/router/routes/JavaScriptBasics.js

	Content:		Content:

2020-11-16T09:36:19Z

2020-11-13T14:39:12Z

Exits for OData V4 Services

← Nächstältere Version		Version vom 13. November 2020, 16:39 Uhr
Zeile 118:		Zeile 118:
	CDS definition in ''/srv/server.js'' defines with <code>.with(require("./lib/handlers"))</code> where to look for exit handlers.		CDS definition in ''/srv/server.js'' defines with <code>.with(require("./lib/handlers"))</code> where to look for exit handlers.

	~~<listing-here>~~		Listing: https://github.com/mattxdev/openSAPHANA/blob/master/srv/lib/handlers/index.js

	[[Category:JavaScript]]		[[Category:JavaScript]]
	[[Category:SAP]]		[[Category:SAP]]
	[[Category:HANA]]		[[Category:HANA]]

2020-11-13T14:05:22Z

Exits for OData V4 Services

← Nächstältere Version		Version vom 13. November 2020, 16:05 Uhr
Zeile 77:		Zeile 77:
	* HANA SQL views (as the example below)		* HANA SQL views (as the example below)
	* Calculation Views		* Calculation Views
			* Synonyms for Calculation Views

	They can be extended on the service level like this:		They can be extended on the service level like this:

2020-11-13T14:01:00Z

Exits for OData V4 Services

← Nächstältere Version		Version vom 13. November 2020, 16:01 Uhr
Zeile 72:		Zeile 72:
	== Exits for OData V4 Services ==		== Exits for OData V4 Services ==

	Data models for OData V4 Services can be based on CDS views ~~or even~~ HANA SQL views (as the example below) ~~and~~ extended on the service level like this:		Data models for OData V4 Services can be based on:

			* CDS views
			* HANA SQL views (as the example below)
			* Calculation Views

			They can be extended on the service level like this:

	using PURCHASE_ORDER_ITEM_VIEW as ItemsView from '../db/data-model';		using PURCHASE_ORDER_ITEM_VIEW as ItemsView from '../db/data-model';

2020-11-13T13:13:31Z

Exits for OData V4 Services

← Nächstältere Version		Version vom 13. November 2020, 15:13 Uhr
Zeile 72:		Zeile 72:
	== Exits for OData V4 Services ==		== Exits for OData V4 Services ==

	Data models for OData V4 Services can be extended on the service level like this:		Data models for OData V4 Services can be based on CDS views or even HANA SQL views (as the example below) and extended on the service level like this:

	using PURCHASE_ORDER_ITEM_VIEW as ItemsView from '../db/data-model';		using PURCHASE_ORDER_ITEM_VIEW as ItemsView from '../db/data-model';

	service CatalogService {		service CatalogService {

2020-11-13T12:39:32Z

Exits for OData V4 Services

← Nächstältere Version		Version vom 13. November 2020, 14:39 Uhr
Zeile 71:		Zeile 71:

	== Exits for OData V4 Services ==		== Exits for OData V4 Services ==

			Data models for OData V4 Services can be extended on the service level like this:

			using PURCHASE_ORDER_ITEM_VIEW as ItemsView from '../db/data-model';

			service CatalogService {

			...

			extend ItemsView with {
			PARTNERS: association to BuyerView on PARTNERS.PARTNERID = PARTNER_ID;
			}

			entity POItemsView @(
			title: '{i18n>poService}',
			Capabilities: {
			InsertRestrictions: {Insertable: false},
			UpdateRestrictions: {Updatable: false},
			DeleteRestrictions: {Deletable: false}
			}
			) as projection on ItemsView;

			...
			}

	Exits for OData V4 Services in Node.js are possible for:		Exits for OData V4 Services in Node.js are possible for:

2020-11-13T11:17:55Z

Exits for OData V4 Services

← Nächstältere Version		Version vom 13. November 2020, 13:17 Uhr
Zeile 74:		Zeile 74:
	Exits for OData V4 Services in Node.js are possible for:		Exits for OData V4 Services in Node.js are possible for:

	* Before; After		* Before
	** Create		* On
	** Read		* After
	** Update
	** Delete		for operations:

			* Create
			* Read
			* Update
			* Delete

	CDS definition in ''/srv/server.js'' defines with <code>.with(require("./lib/handlers"))</code> where to look for exit handlers.		CDS definition in ''/srv/server.js'' defines with <code>.with(require("./lib/handlers"))</code> where to look for exit handlers.

2020-11-13T11:13:18Z

Exits for OData V4 Services

← Nächstältere Version		Version vom 13. November 2020, 13:13 Uhr
Zeile 72:		Zeile 72:
	== Exits for OData V4 Services ==		== Exits for OData V4 Services ==

	Exits for ~~i.e. Create, Read, Update or Delete in~~ OData V4 Services ~~will be created~~ in Node.js		Exits for OData V4 Services in Node.js are possible for:

			* Before; After
			** Create
			** Read
			** Update
			** Delete

			CDS definition in ''/srv/server.js'' defines with <code>.with(require("./lib/handlers"))</code> where to look for exit handlers.

	<listing-here>		<listing-here>