specifically, i am using mysql and am coming from a php environment
where i learned to love PDO. the most important point of pdo is the
use of DBI "context variables" rather than the error-prone use of
question-marks embedded in a query.
many people seem to recommend "sequel". is this something more geared
for the micro$oft database, or is sequel truly generic in nature,
working equally well with all databases?
ActiveRecord and Sequel are the most widely used database mapper
libraries
in the Ruby world. They both support a large number of different
database
backends. Both also support the "named placeholder" feature that you
mention:
User.where("first_name = :name OR last_name = :name", :name =>
"Harrison")
···
On Thu, Oct 31, 2013, at 16:14, mark edwards wrote:
hello - i see this topic was partially covered in an earlier post:
specifically, i am using mysql and am coming from a php environment
where i learned to love PDO. the most important point of pdo is the
use of DBI "context variables" rather than the error-prone use of
question-marks embedded in a query.
many people seem to recommend "sequel". is this something more geared
for the micro$oft database, or is sequel truly generic in nature,
working equally well with all databases?
On 1 Νοε 2013, at 13:46 , mark edwards <lists@ruby-forum.com> wrote:
--
The wise man said: "Never argue with an idiot. They bring you down to their level and beat you with experience."
AFAIK there has been no activity on the core DataMapper codebase
for more than a year, so if starting a new project today I would
probably not consider using it.
···
On Fri, Nov 1, 2013, at 9:15, sto.mar@web.de wrote:
Am 31.10.2013 18:53, schrieb Lars Haugseth:
> ActiveRecord and Sequel are the most widely used database mapper
> libraries in the Ruby world.