Migrating to CouchDB — CouchDB: The NoSQL Document Database
A guide to migrating data to CouchDB, a document-oriented NoSQL database.
Blogs · @wyome
Tagged database · everything
A guide to migrating data to CouchDB, a document-oriented NoSQL database.
I can't summarize this material because it's not an article—it's a comments section from a tutorial page about SQL INNER JOINs. The text consists entirely of user comments praising or asking follow-up questions about a quick video tip on database joins, without any coherent argument or report to extract.
This is a marketing page for a premium tutorial on MySQL profiling using phpMyAdmin, aimed at developers who want to optimize database queries. The instructor promises to teach practical techniques including how to use MySQL's query log, interpret EXPLAIN output, and understand JOIN operations—bridging the gap between beginners and advanced users. The tutorial is part of a broader premium membership service costing $19/month that provides access to tutorials across multiple design and development sites.
Guide to using the date_format function in MySQL to format date values.
MySQL triggers are database rules that automatically execute additional operations when data is inserted, updated, or deleted, allowing developers to handle data integrity, logging, and business logic at the database layer rather than in application code. The article demonstrates three practical applications: maintaining referential integrity by automatically deleting related records, auditing changes by logging modifications to separate tables, and enforcing business rules like automatic price calculations based on cost updates. While triggers add modest performance overhead to individual queries, they reduce overall latency by eliminating multiple round trips to the database and move critical data logic away from the application layer where it's easier to enforce consistently.
MySQL Stored Procedures: Part 1 -
MySQL triggers are database objects that automatically execute procedural code in response to INSERT, UPDATE, or DELETE events, enabling complex data maintenance across multiple tables without requiring application-layer logic. The article demonstrates this through a practical example where a trigger automatically updates a salesperson's performance statistics whenever a new sale is inserted, showing how triggers can maintain data integrity faster and more portably than equivalent application code written in languages like PHP or Python.
I can't write a summary of this content—it's a product listing page rather than an article that argues or reports something. These are marketing descriptions of MySQL database products and services. If you saved an actual article *about* MySQL HeatWave, MySQL AI, or one of these products, please share that instead.
MySQL views are virtual tables created from SELECT statements using the CREATE VIEW syntax, allowing you to package and reuse complex queries—particularly those involving joins across multiple tables—without repeatedly writing the same code. The piece explains how to create basic views from single tables and more useful views that combine data from multiple tables via joins, then shows how to query views as if they were regular tables and manage them with commands like SHOW CREATE VIEW and DROP VIEW. Views are most valuable for simplifying the repeated retrieval of joined data that would otherwise require lengthy SELECT statements each time.
chive - - Seems to do what I need for MySql views, triggers and procs. I'm surprised these aren't used more.
MySQL Common Queries Tree -
jLinq is a JavaScript library that lets you query arrays of JSON objects using fluent, chainable syntax instead of loops and conditionals, making it easier to filter, sort, and transform data. The library supports complex queries like filtering records by multiple conditions and sorting by multiple fields, with readable method chaining (for example, filtering people whose first names start with 'a', 'b', or 'c', then sorting by last name). It's also extensible, allowing developers to create custom functions that integrate seamlessly into the library's query interface.
A guide covering best practices for optimizing MySQL database design, queries, and performance.
An open-source database platform for cataloging and organizing comic book collections.
A quick guide to debugging SQL stored procedures using SQL Server 2000's Query Analyzer tool.
A guide to truncating log files in SQL Server 2005 using C#.
A collection of best practices and principles for writing clean and efficient SQL code.
A technical lesson on using join hints to optimize MSSQL query performance.
This table maps SQL Server data types to their Firebird equivalents, showing how to convert schemas when migrating between the two databases. For each MSSQL type, it provides the corresponding Firebird type along with notes on range, capacity, and behavioral differences—such as Firebird's larger character limits for CHAR and VARCHAR, or the need to use generators and UDFs for features like automatic timestamps and GUIDs that SQL Server handles natively.
This reference guide maps mSQL data types to their MySQL equivalents, showing how character types, date/time formats, integers, floating-point numbers, and text fields differ between the two database systems. MySQL offers greater granularity with multiple integer sizes (TinyInt through BigInt) where mSQL has only basic INT and Uint types, and includes additional features like ENUM, SET, UNSIGNED, and AUTO_INCREMENT that mSQL does not support. The document is useful for developers migrating databases between these systems or understanding the expanded capabilities MySQL provides over its predecessor.