Yes, Marko's BaseTen is excellent, and the PostgreSQL support for the Mac as a
platform is quite good. The only downside really, is that there is an
outstanding issue with regards to collation in certain locales on BSD based
systems, of which OS X is one, so long as you are us_EN and UTF-8, you
Flavio,
> Well... That's a good enough reason. Driving that Sun stuff through exec()
> and command-line utilities should be extremely painful and hard to maintain
> in the future.
>
Indeed, I did consider that for about 5 seconds, then smacked myself in the
forehead...
> Do you really need to u
Josh,
> Unfortunately, the other key piece of information I have left out is that I
> also need to tie into some C based APIs in order to drive some large Sun
> robotic tape libraries. I also wish to achieve as high a degree of
> concurrency as possible in the file moving/compression processes
Flavio,
> > The application is essentially a server side app that will manage various
> > background file moving/archiving processes and store metadata about the
> > files in a database. The heavy lifting in terms of file analysis and
> > moving the materials around and storing the metadata in
Josh,
On Apr 28, 2010, at 10:57 AM, Joshua Tidsbury wrote:
> The application is essentially a server side app that will manage various
> background file moving/archiving processes and store metadata about the files
> in a database. The heavy lifting in terms of file analysis and moving the
>
On Apr 28, 2010, at 10:57 AM, Joshua Tidsbury wrote:
I haven't yet decided on the framework for the web app (often use
Rails for standalone web apps, may use PHP), but just don't want to
box myself into a corner by a bad decision early on. Obviously, the
notion of being able to use Core D
Thank you all for your helpful replies so far - greatly appreciated!
To add some clarity: The application is essentially a server side app that will
manage various background file moving/archiving processes and store metadata
about the files in a database. The heavy lifting in terms of file ana
On Apr 28, 2010, at 10:35 AM, Jens Alfke wrote:
> SQLite works fine with multiple clients — it uses file locking to support
> transactions and ACID properties. I’ve used it that way myself. It just
> doesn’t scale as well as a full server-based system, because doing locking
> via the filesyste
On Apr 27, 2010, at 6:04 PM, Joshua Tidsbury wrote:
> The application I am going to be writing ultimately needs to access MySQL as
> a datastore. I'd love to go with Core Data and SQLite, but based on some
> reading, SQLite wouldn't be ideal if multiple clients were to be accessing
> the same
Are you trying to write a MySQL client or are you trying to store stuff into
MySQL?
On 28 April 2010 17:58, Dru Satori wrote:
> Well, the short version is CoreData & SQLLite will not help you in any way
> with MySQL. As to using another framework or rolling your own, that largely
> depends upon
Well, the short version is CoreData & SQLLite will not help you in any way with
MySQL. As to using another framework or rolling your own, that largely depends
upon your needs. Obviously the GPL is not an issue if you are going against
MySQL anyways, so I would probably look hard at not reinven
Hello everyone,
I'm in the process of developing one of my first Cocoa applications, and I'm
looking for some advice to keep myself from wandering into the wrong direction.
The application I am going to be writing ultimately needs to access MySQL as a
datastore. I'd love to go with Core Data an
12 matches
Mail list logo
