If yes, how do I set it up in the yml file? Thanks.
- amateur Railist
A chill runs down my spine.
Scott Thorpe wrote:
A chill runs down my spine.
^ What he said.
Joe
Scott Thorpe wrote:
A chill runs down my spine.
Access really isn’t bad for small applications. And it’s good to learn
on because if you can’t figure the SQL out for something, the query
wizard will show you what you’re missing.
–
Austin G.
Thinking & Making: IA, UX, and IxD
http://thinkingandmaking.com
[email protected]
On 8/18/06, Austin G. [email protected] wrote:
Scott Thorpe wrote:
A chill runs down my spine.
Access really isn’t bad for small applications. And it’s good to learn
on because if you can’t figure the SQL out for something, the query
wizard will show you what you’re missing.
It’s one of the worst databases to learn on. You want to learn on a
database that enforces good habits right from the start and uses an
SQL dialect that is as standards compliant as possible. Access has
it’s uses, but Access and SQL just shouldn’t be used in the same
sentence IMO.
If you’ve got any say in it, I’d suggest you use SQLite in place of
Access. It works fine on Windows and Linux, is rock solid under
Rails, costs nothing, is trivial to implement (i.e. copy one .EXE and
one .DLL into your ruby\bin directory) and is a much better fit as a
small Web-app database.
Regards
Dave M.
I don’t remember Access having bad basic SQL (T-SQL), it was all the
other crap like forms, etc., its absolutely horrible security scheme,
and its almost complete uselessness used as a server. When I started
using MySQL back in its 3.x days, I fondly recalled Access’ foreign key
support.
Joe
On 8/18/06, David M. [email protected] wrote:
If you’ve got any say in it, I’d suggest you use SQLite in place of
Access. It works fine on Windows and Linux, is rock solid under
Rails, costs nothing, is trivial to implement (i.e. copy one .EXE and
one .DLL into your ruby\bin directory) and is a much better fit as a
small Web-app database.
Why SQLite over MySQL?
–
Austin G.
Thinking & Making: IA, UX, and IxD
http://thinkingandmaking.com
[email protected]
On 18-aug-2006, at 22:15, Austin G. wrote:
Access really isn’t bad for small applications.
As often as small means “1 person who bought it and runs exclusively
on Windows and has filesystem access and can manage ODBC” it might be
workable.
Please don’t.
Julian ‘Julik’ Tarkhanov
please send all personal mail to
me at julik.nl
Joe R. wrote:
I don’t remember Access having bad basic SQL (T-SQL), it was all the
other crap like forms, etc., its absolutely horrible security scheme,
and its almost complete uselessness used as a server. When I started
using MySQL back in its 3.x days, I fondly recalled Access’ foreign key
support.
I’ll agree with that. Access has quite a nice query designer and allows
you to quickly manipulate data with a decent GUI. Its often used as a
data format, though I wouldn’t recommend it due to the required
maintenance routine you would have to run periodically.
Never build a production forms app with it though ! (been there, got the
scars)
I’ve recently used the Ruby DBI ODBC adapter with Access, and got it
connected very quickly. No experience with non-trivial use however.
On 19/08/06, Austin G. [email protected] wrote:
On 8/18/06, David M. [email protected] wrote:
If you’ve got any say in it, I’d suggest you use SQLite in place of
Access. It works fine on Windows and Linux, is rock solid under
Rails, costs nothing, is trivial to implement (i.e. copy one .EXE and
one .DLL into your ruby\bin directory) and is a much better fit as a
small Web-app database.Why SQLite over MySQL?
I’m assuming one of the reasons he’d want to use Access at all is
because it’s a single file database, and there’s not a lot of data to
deal with. SQLite is the closest match, and has a lot of things going
for it as a Rails DB.
A really handy feature of Access being a single file is that taking a
backup of an Access database is pretty trivial - SQLite is the same.
Backing up MySQL is more complicated (not much more, but definitely
more).
While MySQL is bigger, more powerful, …, it comes with a different
set of characteristics; it’s “more different” from Access than SQLite.
In any case, it’s fairly simple to move from one database app to
another within Rails, once you’re up and going. If MySQL rocks your
boat, go with it and you’ll be absolutely fine.
Regards
Dave M.
FWIW, I recently migrated a legacy Access MDB backed app to Rails &
MySQL. I
found Navicat MySQL (commercial software) to be immensely helpful in
exporting the data. Other options (CSV, etc) were trickier (mostly
extended
character set issues).
I’ve done Access MDB apps in the past and would only do so now under
duress.
I think the SQLite suggestion is an excellent one, both in the general
light-weight DB case, and in the specific single-file case if indeed
that’s
what the OP’s concern was.