SEO

Hi,

I'm wanting to build a database and interface for a small business to
keep track of things such as clients, suppliers etc. The database will
be served on a Linux box, with users accessing/updating it over the
network from both Linux and windows.

I'm wondering if I could get some suggestions as to how implement this
quickly and simply? I was thinking a web interface using PHP would be
the fastest way of going about it.

I have a understanding of SQL and can program but I don't want to spend
an eternity working on it and maintaining it.

Thank you

--
Rory Hart

Lifestyle Management Consultant

Professional Lifestyle Management
http://www.lifestylemanage.com

Phone 03 9879 5643 PO Box 4179
Fax 03 9879 6743 Ringwood Vic 3134
Mobile 0412 821030 Australia


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Rory Hart wrote:
> Hi,
>
> I'm wanting to build a database and interface for a small business to
> keep track of things such as clients, suppliers etc. The database will
> be served on a Linux box, with users accessing/updating it over the
> network from both Linux and windows.
>
> I'm wondering if I could get some suggestions as to how implement this
> quickly and simply? I was thinking a web interface using PHP would be
> the fastest way of going about it.

A web interface will make it easy for others to use (and from anywhere).
OTOH, if you're comfortable with C# or Java or "X" you could do it that
way, however that will mean either installing an app or applet on each PC.

> I have a understanding of SQL and can program but I don't want to spend
> an eternity working on it and maintaining it.

What languages are you comfortable with? PHP, Ruby, Python, Perl all
work well for web interfaces. C#, Java (and others) work fine as client
apps..

--
Postgresql & php tutorials
http://www.designmagick.com/

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Chris wrote:

> Rory Hart wrote:
>
>> Hi,
>>
>> I'm wanting to build a database and interface for a small business to
>> keep track of things such as clients, suppliers etc. The database
>> will be served on a Linux box, with users accessing/updating it over
>> the network from both Linux and windows.
>>
>> I'm wondering if I could get some suggestions as to how implement
>> this quickly and simply? I was thinking a web interface using PHP
>> would be the fastest way of going about it.
>
>
> A web interface will make it easy for others to use (and from
> anywhere). OTOH, if you're comfortable with C# or Java or "X" you
> could do it that way, however that will mean either installing an app
> or applet on each PC.
>
>> I have a understanding of SQL and can program but I don't want to
>> spend an eternity working on it and maintaining it.
>
>
> What languages are you comfortable with? PHP, Ruby, Python, Perl all
> work well for web interfaces. C#, Java (and others) work fine as
> client apps..
>
PHP would be my choice i think, there are libraries and tools for using
pgsql and php aren't there?

--
Rory Hart

Lifestyle Management Consultant

Professional Lifestyle Management
http://www.lifestylemanage.com

Phone 03 9879 5643 PO Box 4179
Fax 03 9879 6743 Ringwood Vic 3134
Mobile 0412 821030 Australia


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Rory Hart wrote:
> Chris wrote:
>
>> Rory Hart wrote:
>>
>>> Hi,
>>>
>>> I'm wanting to build a database and interface for a small business to
>>> keep track of things such as clients, suppliers etc. The database
>>> will be served on a Linux box, with users accessing/updating it over
>>> the network from both Linux and windows.
>>>
>>> I'm wondering if I could get some suggestions as to how implement
>>> this quickly and simply? I was thinking a web interface using PHP
>>> would be the fastest way of going about it.
>>
>>
>>
>> A web interface will make it easy for others to use (and from
>> anywhere). OTOH, if you're comfortable with C# or Java or "X" you
>> could do it that way, however that will mean either installing an app
>> or applet on each PC.
>>
>>> I have a understanding of SQL and can program but I don't want to
>>> spend an eternity working on it and maintaining it.
>>
>>
>>
>> What languages are you comfortable with? PHP, Ruby, Python, Perl all
>> work well for web interfaces. C#, Java (and others) work fine as
>> client apps..
>>
> PHP would be my choice i think, there are libraries and tools for using
> pgsql and php aren't there?
>

Of course. Shameless plug coming up

http://www.designmagick.com/category/2/Starting-Out

--
Postgresql & php tutorials
http://www.designmagick.com/

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Chris wrote:

>
> Of course. Shameless plug coming up
>
> http://www.designmagick.com/category/2/Starting-Out
>

Thanks ^_^

--
Rory Hart

Lifestyle Management Consultant

Professional Lifestyle Management
http://www.lifestylemanage.com

Phone 03 9879 5643 PO Box 4179
Fax 03 9879 6743 Ringwood Vic 3134
Mobile 0412 821030 Australia


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

> >> I'm wondering if I could get some suggestions as to how implement
> >> this quickly and simply? I was thinking a web interface using PHP
> >> would be the fastest way of going about it.
> >

If you used Ruby on Rails, you'd be finished by now. It slices, it
dices, it makes julienne fries.

Seriously, it's not too bad if you don't mind it's plentiful
shortcomings. I was getting carpal tunnel syndrome from typing
<scripting language> pages so I switched to RoR for a hobby app. It
works fine, but you have to do it "The Rails Way" and expect no help
from the "Community" because they are a fanboi cheerleader squad, not
interested in silly stuff like referential integrity, functions,
triggers, etc. All that nonsense belongs in the application!

Check this out, there is no stale connection detection or handling in
rails. I'm not kidding. If you connection drops out, restart your
web server. Sorry. Blah.

Anyway, besides its warts, it is dead easy to use, and does make
putting together web applications in a "green field" scenario quite
painless. Just don't try to do anything outside the box like trying
to access an existing database that uses RDBMS features heavily and
uses normal object naming.

- Ian

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Ian Harding wrote:

I am fascinated by your post. I have never heard a bad thing said about
RoR.

I have been meaning to investigate it because it is the only system I've
heard of that makes the same claim that I do, which is to have
eliminated entire categories of labor through automation.

Except that I built mine on a database foundation. Systematize and
automate database handling and UI creation should follow. I did not
know that RoR was so cavalier w/respect to the database, is that really
true? Is it really just yet-another-UI system?

IMHO the problem with all blink-of-an-eye dev tools is that they are not
built on a foundation of solid database design, but now we're drifting
OT....

>>>>I'm wondering if I could get some suggestions as to how implement
>>>>this quickly and simply? I was thinking a web interface using PHP
>>>>would be the fastest way of going about it.
>>>>
>>>>
>
>If you used Ruby on Rails, you'd be finished by now. It slices, it
>dices, it makes julienne fries.
>
>Seriously, it's not too bad if you don't mind it's plentiful
>shortcomings. I was getting carpal tunnel syndrome from typing
><scripting language> pages so I switched to RoR for a hobby app. It
>works fine, but you have to do it "The Rails Way" and expect no help
>from the "Community" because they are a fanboi cheerleader squad, not
>interested in silly stuff like referential integrity, functions,
>triggers, etc. All that nonsense belongs in the application!
>
>Check this out, there is no stale connection detection or handling in
>rails. I'm not kidding. If you connection drops out, restart your
>web server. Sorry. Blah.
>
>Anyway, besides its warts, it is dead easy to use, and does make
>putting together web applications in a "green field" scenario quite
>painless. Just don't try to do anything outside the box like trying
>to access an existing database that uses RDBMS features heavily and
>uses normal object naming.
>
>- Ian
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: explain analyze is your friend
>
>



---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

On 3/29/06, Ian Harding <iharding@destinydata.com> wrote:
>
> Seriously, it's not too bad if you don't mind it's plentiful
> shortcomings. I was getting carpal tunnel syndrome from typing
> <scripting language> pages so I switched to RoR for a hobby app. It
> works fine, but you have to do it "The Rails Way" and expect no help
> from the "Community" because they are a fanboi cheerleader squad, not
> interested in silly stuff like referential integrity, functions,
> triggers, etc. All that nonsense belongs in the application!
> ...


That's an eye opener, thanks Ian.

t.n.a.

Kenneth Downs wrote:

> I have been meaning to investigate it because it is the only system I've
> heard of that makes the same claim that I do, which is to have
> eliminated entire categories of labor through automation.

Have you looked at http://catalyst.perl.org/ lately?
IMHO it's "Rails done right" and it's perl, so it just /has/ to be good ;-)

sorry, couldn't resist.
bkw


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

On Mar 29, 2006, at 8:03 AM, Kenneth Downs wrote:

> Ian Harding wrote:
>
> I am fascinated by your post. I have never heard a bad thing said
> about RoR.
>
> I have been meaning to investigate it because it is the only system
> I've heard of that makes the same claim that I do, which is to have
> eliminated entire categories of labor through automation.
>
> Except that I built mine on a database foundation. Systematize and
> automate database handling and UI creation should follow. I did
> not know that RoR was so cavalier w/respect to the database, is
> that really true? Is it really just yet-another-UI system?

Pretty much, AFAICT, it's designed to run with anything that supports
SQL as it's
embedded store, rather than allowing you to talk to an RDBMS with an
existing
schema easily.

It's the exact opposite there of OpenACS, which puts tentacles deep
into the database,
and really relies on embedded functions and well crafted SQL. And
only supports
Oracle and PostgreSQL, not MySQL. I'm playing with Perl+Catalyst+DBIx
at the
moment, which seems to be a reasonable compromise, as long as you
really like
perl. .

For the original poster - a web interface might well be the simplest
to put together,
but if a client turns out to be a better solution I'd strongly
suggest looking at Qt.
It has nice SQL support and it's very quick to turn around a simple
database
access application, if you've a passing acquaintance with C++. And
it'll compile
to Windows, Linux and OS X from the same source.

Cheers,
Steve


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings