This website requires JavaScript.
Explore
Help
Sign In
[ LincPay Solutions Private Limited ]
{"secure":"✓","seamless":"✓","swift":"✓","status":"
🚀
Ready to Ship"}
CBSNexora
/
cbsnexora-backend
Watch
4
Star
0
Fork
0
Code
Issues
Pull Requests
Actions
28
Packages
Projects
Releases
Wiki
Activity
Files
8feb9980f368e04471e3e761ecedcfb67b5d0068
cbsnexora-backend
/
mifosng-db
/
patches-beta-3-heavens-family
T
History
Keith Woodlock
8feb9980f3
remove organisation and anything org_id related
2012-07-14 23:38:51 +01:00
..
patch-0001-fund-and-loanproduct-changes.sql
support schema per tenant multi-tenancy. basic auth security filter is extended to detect tenant-id header on request, verify tenant id is valid and then use provided credentials to authenticate user details against users on the tenant specific schema.
2012-07-13 18:05:43 +01:00
patch-0002-fund-and-loan-changes.sql
support schema per tenant multi-tenancy. basic auth security filter is extended to detect tenant-id header on request, verify tenant id is valid and then use provided credentials to authenticate user details against users on the tenant specific schema.
2012-07-13 18:05:43 +01:00
patch-0005-branch-transfer-of-funds.sql
support schema per tenant multi-tenancy. basic auth security filter is extended to detect tenant-id header on request, verify tenant id is valid and then use provided credentials to authenticate user details against users on the tenant specific schema.
2012-07-13 18:05:43 +01:00
patch-0006-office-transactions.sql
support schema per tenant multi-tenancy. basic auth security filter is extended to detect tenant-id header on request, verify tenant id is valid and then use provided credentials to authenticate user details against users on the tenant specific schema.
2012-07-13 18:05:43 +01:00
patch-0007-remove-organisations.sql
remove organisation and anything org_id related
2012-07-14 23:38:51 +01:00
WIPdbchanges.sql
support schema per tenant multi-tenancy. basic auth security filter is extended to detect tenant-id header on request, verify tenant id is valid and then use provided credentials to authenticate user details against users on the tenant specific schema.
2012-07-13 18:05:43 +01:00