Libraries tagged by prepared

Temporarily enable/disable PDO prepared statement emulation

Go to Download

A simple PDO query interface with support for result set and row level caching

Go to Download

GrumpyPDO for PHP

Go to Download

TYPO3 Questions - FAQ by coding.ms: Frequently asked questions (FAQ) for TYPO3 with SEO-optimized output, prepared schema.org microdata, markdown support for answers, shop-product integration, category and keyword filters, backend question management, CSV export, and improved AI visibility (GEO). Suitable for structured FAQ pages, product-related questions, and recurring knowledge in websites or intranets.

Go to Download

A lightweight PDO helper for MySQL and SQL Server with prepared queries, transactions, and connection lifecycle utilities.

Go to Download

Add an easy to use grid element for Container. It's Framework independent. Prepared for Bootstrap.

Go to Download

PHP class library for simple, convenient, fast and safe work with MySql database, using PHP mysqli extension and imitation of prepared queries.

Go to Download

MyBatis-style SQL mapper: mark an interface #[Mapper] and its methods #[Select]/#[Insert]/#[Update]/#[Delete] with the SQL. A build-time processor compiles a reflection-free Cache\ implementation (prepared statements, #{name} bound params, optional row->object hydration) and registers it as a container bean keyed by the interface. Self-contained: a bundled DatabaseConfig provides the 'PDO' bean from a [database] group in the app's app.ini, so you only edit config. Runtime is PHP 5.3-safe.

Go to Download

PHP MySQL Wrapper which utilizes MySQLi and prepared statements

Go to Download

Codesniffer & phpstan prepared configs for easy-to-use. Rewritten by contributte's authors.

Go to Download

Lightweight PHP MySQL wrapper with prepared statements. Query returns MySQL object - call fetchAssoc() or fetchAll() to get data.

Go to Download

Php Adaptive Microframework

Go to Download

Php Adaptive Microframework

Go to Download

Php Adaptive Microframework

Go to Download

##### API Overview - Accounts list and balance - Transaction overview (also for saving accounts) - Payments import - Statement list and download - FX rates ##### Authentication Before making a call to Premium API, you need to register your app at our _Developer portal_. This is where you get the **ClientID** that your application must send in the request as `X-IBM-Client-Id`. This is the key that grants your app access to the API. However, this may not be enough. Your application needs to use mTLS to call most operations here. Thus, you not only need _https_ but also a client certificate issued by us. The exception is two operations for FX rates that are accessible also without a client certificate. Each bank client/user can issue several certificates. Each certificate can permit different sets of operations (http methods) on different bank accounts. All this must be configured in Internet Banking first by each bank client/user (bank clients need to look under _Settings_ and do not forget to download the certificate at the last step). The certificate is downloaded in **PKCS#12** format as **\*.p12** file and protected by a password chosen by the bank client/user. Yes, your app needs the password as well to get use of the **\*p12** file for establishing mTLS connection to the bank. Client certificates issued in Internet Banking for bank clients/users have limited validity (e.g. **5 years**). However, **each year** certificates are automatically blocked and bank client/user must unblock them in Internet Banking. It is possible to do it in advance and prolong the time before the certificate is blocked. Your app should be prepared for these scenarios and it should communicate such cases to your user in advance to provide seamless service and high user-experience of your app. ##### Rate Limiting The number of requests in each API operation is limited to 10 per client per sliding second and 5000 per client per sliding day. The exception is the 'Download Statement' operation with the limits lowered to 5 per client per sliding second and 1500 per client per sliding day. This is because it transports potentially sizeable binary files. The consumer must be able to handle HTTP status 429 in case of exceeding these limits. Response headers `X-RateLimit-Limit-Second` and `X-RateLimit-Limit-Day` show the actual limits configured for the specific operation. Response headers `X-RateLimit-Remaining-Second` and `X-RateLimit-Remaining-Day` are returned to help prevent the limits from being exceeded. ##### Notes Be aware, that in certain error situations, API can return specific error structures along with 5xx status code, which is not explicitely defined below. ##### Quick Start Client Feel free to download a simple Java client that gives you quick access to our API.

Go to Download