OData is quickly becoming the Lingua Franca for data exchange over the
web. The OData standard defines a protocol and a language structure for
issuing queries and updates to remote data sources, including (but not
limited to) relational databases, file systems, content management systems,
and traditional web sites. It builds upon existing Web technologies, like
HTTP and RESTful web services, the Atom Publishing Protocol (AtomPub), XML,
SAP and Sybase iAnywhere released SQL Anywhere version 16 in March 2013, and
it had many cool new features. This blog post will cover one specific
enhancement, the new support for OData access to SA databases.
Note: SA 16.0 is the follow-on release to version 12.0.1. There was no
version 13, 14, or 15.
SQL Anywhere actually introduced support for SOAP and REST-based web services
Every software development project of any significant size or complexity has
a requirement for controlling the source code asset. PowerBuilder is capable
of integrating with any third-party Source Code Control (SCC) tool that
implements Microsoft's SCC API. However, the fact that PowerBuilder stores
its code inside PowerBuilder Libraries (PBLs) and not as individual ASCII
text files adds a layer of complexity to that integration. The release of
PowerBuilder 8.0 in 2001 brought with it a new set of challenges in the form
of a completely redesigned interface with SCC providers, inc... (more)
When Sybase first released the Unwired Platform in 2008, it was intended to
be a complete end-to-end development environment for mobile applications.
SUP developers would create the middle tier components (a.k.a. Mobile
Business Objects), and the client application executables from a single,
integrated Eclipse-based toolset. There was a "PowerBuilder-like" 4GL
screen painter, called the Device Application Designer (or DAD), that
compiled down to native Blackberry 5/6 or Windows Mobile 6.5 applications.
(Yes, it's hard to imagine, but there was a time when iOS devices were not ... (more)
Every development shop that is currently managing its PowerBuilder source
code with a third-party SCC tool and has not yet migrated to PB8 will need to
understand the upcoming changes in methodology before attempting a migration.
Even PBNative users will be affected, as that interface has been redesigned
to use the SCC interface as well.
In my previous article, "Understanding the SCC Interface in PowerBuilder 8"
(PBDJ, Vol. 8, issue 11), I outlined the sweeping rewrite of the source code
control (SCC) interface introduced in PowerBuilder 8.0. This article walks
through some simp... (more)
Source code control (SCC) has become a "hot topic" lately, especially after
PowerBuilder 8.0 was released, as it contains a wholesale revision to its
interface with third-party SCC tools.
PB8 now leverages the full functionality of Microsoft's SCC API, and is much
more tightly integrated with the SCC repository. There are now over a dozen
commercially available SCC tools that implement the SCC API, and choosing the
appropriate tool for your organization is not a trivial task. The scope,
features, and functions of these tools range from the "bare bones" approach
of the open-sourc... (more)