Dale wrote:
> Hi Wiggins d'Anconia, you wrote :
>
>> Dale wrote:
>> [snip]
>>
>>>
>>> I think a bit of background is needed. I work for the helpdesk of an
>>> ISP. The space I've got is a staff account which mirrors the service
>>> the residential customers receive. It's got a cgi-bin (of cours
Hi Wiggins d'Anconia, you wrote :
Dale wrote:
[snip]
I think a bit of background is needed. I work for the helpdesk of an
ISP. The space I've got is a staff account which mirrors the service
the residential customers receive. It's got a cgi-bin (of course,
otherwise there wouldn't be any po
>>> Just one thing though - I need to have DBD::SQLite installed on my
>>> server and it's not on there, nor will it be (again, not my choice).
>>> I'm still up a certain creek without a paddle *grin*
>>
>> Well, that one is between you and your admins, but Perl development
>> is *significantly* e
Dale wrote:
[snip]
>
> I think a bit of background is needed. I work for the helpdesk of an
> ISP. The space I've got is a staff account which mirrors the service
> the residential customers receive. It's got a cgi-bin (of course,
> otherwise there wouldn't be any point in my script *grin*) but
Hi Chris Devers, you wrote :
On Tue, 14 Jun 2005, Dale wrote:
Hi Chris Devers, you wrote:
>You miss the point of SQLite then.
You're right, I have. I assumed it would need SQL to work. Thanks for
correcting me! :)
You're still confused, I think, though it's not quite your fault :-)
It *
On Tue, 14 Jun 2005, Dale wrote:
> Hi Chris Devers, you wrote:
>
> >On Mon, 13 Jun 2005, Dale wrote:
> >
> >> However, the server this currently sits on doesn't and won't ever (not
> >> through choice) have any form of SQL so I'll just have to struggle
> >> with the files. :)
> >
> >You miss the p
Hi Chris Devers, you wrote:
On Mon, 13 Jun 2005, Dale wrote:
However, the server this currently sits on doesn't and won't ever (not
through choice) have any form of SQL so I'll just have to struggle
with the files. :)
You miss the point of SQLite then.
You're right, I have. I assumed it w
On Mon, 13 Jun 2005, Dale wrote:
> However, the server this currently sits on doesn't and won't ever (not
> through choice) have any form of SQL so I'll just have to struggle
> with the files. :)
You miss the point of SQLite then.
With SQLite -- or the Perl interface, DBD::SQLite -- you're just
Hi Wiggins d'Anconia, you wrote:
Fair points, I forget SQL::Lite since I wouldn't (need to) use it since
I am already familar with the others. It sure would have been nice to
have SQLite as a first step when I first learned :-). Though I still
think if you have the time and desire to learn a dat
Chris Devers wrote:
> On Mon, 13 Jun 2005, Wiggins d'Anconia wrote:
>
>
>>If you are completely new to SQL/DBs then you might start with MySQL,
>>though I would recommend going with PostgreSQL.
>
>
> I wouldn't.
>
> PostgreSQL is good, but it's pretty complicated, and this problem isn't
> yet.
On Mon, 13 Jun 2005, Wiggins d'Anconia wrote:
> If you are completely new to SQL/DBs then you might start with MySQL,
> though I would recommend going with PostgreSQL.
I wouldn't.
PostgreSQL is good, but it's pretty complicated, and this problem isn't
yet. No need to make it more complicated tha
Dale wrote:
> Hi folks,
>
[snip]
>
> What would the best practice be in this case?
>
> Cheers!
Switch to an RDBMS, period. Your model has grown beyond flat files, and
having the full range of SQL relating, sorting, limiting, and selecting
will serve you well from the description. It will also
12 matches
Mail list logo
