I was recently working on a project where there was an option to export data from the database. The export function simply exported 2 hard-coded columns that were returned by a stored procedure into a tab-delimited text file.
A discussion came up at work recently about the extent of constraint usage in your databases. There were basically 2 camps: 1. Constrain everything humanly possible. If it’s an integer that wouldn’t normally be negative, add a ">= 0" constraint. 2. Constrain primarily where it’s necessary to maintain referential integrity. Consider the following diagram. It’s a map of the flow of data from your user, which eventually makes its way into the database.
This post explains how to export records for individual tables into CSV files using built in mysql functionality.
Not true – you can start with code and create mappings later. In fact, you can write plain-old CLR object like this:
Continuing his series on interview questions, Jesse at 20bits presents a great overview of database indexes and how they work. A must read!
Languages that support multiline quotes such as C#, Perl and PHP make it easy for developers to embed SQL code in applications in a readable and maintainable way
Genuitec is proud to announce the immediate availability of two milestone releases: MyEclipse Enterprise Workbench 6.5 M1 and MyEclipse 6.5 Blue Edition M1. These releases, available in the “development releases” area of the download page, add features and functionality, as well as a peek at what to expect from the general availability release in the coming weeks.
I was writing a very simple Grails application and ran into a problem when I accidentally used a SQL keyword as a property name. This post documents what happened, and how I (pretty easily) fixed it.
For a database application, all security in the end becomes a question of who can read and write to what tables. While this is obvious to veteran database programmers, it is not always so obvious to relative newcomers. A programmer who thinks primarily in terms of code will be used to conceptualizing actions, steps, procedures and so forth. This programmer will therefore think of security in terms of who is allowed to perform what actions. However, when you examine the actions performed by database application code, you find that, no surprise, it is a lot of database reads and writes.
Sponsors
More tags
Technology Apple Design Hardware Linux Programming Security Software unix-linux ajax how-to javascript php java tools .net trends frameworks books research gui web design ruby open source reviews web 2.0 eclipse other languages perl python humor announcement News Movies Microsoft Windows usability standards rss shopping tech server google web services web rails code search mysql hacking business community list OSX art film world backup games reference development flash fun online tips tool maps web2.0 collaboration howto tuning resources tutorial performance opensource service social privacy comics sharing tutorials visualization information administration utilities xml opinion encyclopedia SQL geocoding cheatsheet css-html methodology toolbox web-based amp postgresql join db freebase
Object-oriented databases complement relational databases in important ways, says Anat Gafni, VP of Engineering at db4objects, the company behind the open-source object database db4o. In this interview with Artima, Gafni explains how OO databases support agile development, and how they co-exist with relational databases in an enterprise.
When working with Hibernate, it is *critical* to understand lazy associations, as they can be your best friend, but if you don't treat them right, they can be your worst enemy.
Ian Murdock, Sun vice president of developer and community marketing, and Marten Mickos, head of Sun's database group, used CommunityOne to outline Sun's ideals on recent acquisition MySQL, OpenSolaris and NetBeans. At the same time they explained Sun's attempts to monetize them.
I was cruising the MySQL Forge Worklog when I came across the idea of Time Delayed Replication. I had never considered the benefits of deliberately keeping a slave server behind a master.
Care must be taken when placing conditions on the results of the right-hand table of a LEFT JOIN because it could easily become a normal JOIN since MySQL is using a NULL row for every column in the right-hand table when no records exist.
What does the future bring for the sell of CodeGear to Embarcadero? My take on it.
As mentioned in my previous post, the objective of this series of articles is to share some database design patterns that have helped me in the past to achieve, using a relational database as a backend, an reusable API for data persistence with a higher level of abstraction and flexibility, while still taking advantage of the tooling and previous knowledge of relational databases. In this second post I’ll try to cover a basic concept: the way entities are related to each other.
Embarcadero Technologies, a privately held database tools vendor, today announced a definitive agreement to purchase Borland's CodeGear division for $23 million.
As reported yesterday from CommunityOne: * MySQL Server is and will always remain fully functional and open source, * so will the MySQL Connectors, and * so will the main storage engines we ship.
Setting constraints and rules in the database is better than writing special code to handle the same task since it will prevent another developer from writing a different query that bypasses all of the special code and could leave your database with poor data integrity.
Apurba takes an in-depth look at the Hibernate Query Cache Implementation and some impacts of it on operations like Natural Key Lookup.
Clear explanation of all levels of hibernate caching. It will help grails developers also.
Would you like to see LINQ (Language INtegrated Queries) implemented for Java? This is an invitation to vote for it and to contribute.
There has been a lot of talk lately about PostgreSQL and what MySQL can learn from the PostgreSQL clan. We would like to look at the reverse of that. This article is a bit of a complement to Joshua Drake's What MySQL (and really, Sun) can learn from PostgreSQL. First of all a lot of staunch advocates of PostgreSQL wonder what exactly is it that MySQLers see in that beast of a database or as Martin Mickos likes to call it The Ferrari of databases?
We had a split in storages and search, each part with it’s own Java interface (a component could implement both of course). This way we could have Lucene, database and in-memory search and database and file (XML, plain text) storage. We were very flexible with storage and search this way and people could easily implement different storage backends because developers have been freed from the search implementation.
Reports are circulating that Twitter is already dropping Ruby on Rails, and folks are getting worked up in all sorts of directions. Let's calm down ... this is just a case of asking a tool to act like something it simply is not.
Sometimes we wish to know what locks are being held by the transaction. Also it would be great to know what SPID owns the transaction, on which objects the locks are being held, what SQL statement caused the locks, etc...
On the surface everything is looking smooth: MySQL distributes proprietary MySQL+InnoDB to those who wants to embed them in their proprietary applications The open source community can work with GPL MySQL and GPL InnoDB. In practice it doesn't work quite that way:
We’ve run against multiple (five now) separate PostgreSQL servers for a long time now. To be clear, that’s five separate “databases” in the sense that PostgreSQL uses the term. Not a replicating / mirror setup - separate databases with different data but with similar structure.
OODB vendor Gemstone works on a Ruby VM called MagLev. Working with Seaside's and DabbleDB's Avi Bryant, Gemstone bases the Ruby runtime on their Smalltalk VM to offer performance and powerful persistence features. InfoQ talked to Avi Bryant and Gemstone's Bob Walker about the technology behind MagLev and the plans for it.
The 10.4.1 version of Java DB, the world's most advanced Java database, has some really cool features -- asynchronous replication, table functions and JMX capabilities. Sun engineers worked within the Apache/Derby community to develop these features.
12345678910111213 ... 34 »










