That's alight Jim, I will be suing you for copyright infringement on my
ideas though ;-)
-Original Message-
From: Jim Rising [mailto:cfflex...@jimrising.com]
Sent: 24 April 2009 00:59
To: cf-talk
Subject: Re: YIKES! I must let internet users write SQL queries for our
database!
sorry
Ian,
What about creating a Flex based tool that allows users to choose the table
they want to get the data from and then the columns for the table (that you
wanted to be able to select by) would be available. Basically making a
'drag and drop' kinda query builder. where the users don't type
Rob Parkhill wrote:
What about creating a Flex based tool...
That has potential. The current tool is simple HTML forms that attempt
to do what you describe, but does not flow very well as it currently exists.
~|
AdobeĀ®
Hey Ian,
My first thoughts on this would be to ensure that YOU keep total control
over the actually SQL that is being run, if you're working with large sets
of data (more than a few GB) than the performance problems which arise from
poorly written SQL could likely cause you all kinds of beef ;-)
Ian Skinner wrote:
Did I get your attention? Luckily these are read-only queries, but still!
I forgot to mention an important consideration is to somehow control and
mitigate query requests so that users don't tie up the database with a
task taking hours and hours to process.
It is already a
Did I get your attention? Luckily these are read-only queries, but still!
A couple of things:
1. Create a large selection of views with nice names, it will make it
easier for your users to identify the tables and columns they are
looking for. This will also remove or reduce the need for JOINs
Robert Rawlins - Think Blue wrote:
Hey Ian,
My first thoughts on this would be to ensure that YOU keep total control
over the actually SQL that is being run, if you're working with large sets
of data (more than a few GB) than the performance problems which arise from
poorly written SQL
Skinner [mailto:h...@ilsweb.com]
Sent: 23 April 2009 16:25
To: cf-talk
Subject: Re: YIKES! I must let internet users write SQL queries for our
database!
Robert Rawlins - Think Blue wrote:
Hey Ian,
My first thoughts on this would be to ensure that YOU keep total control
over the actually SQL
...@ilsweb.com]
Sent: 23 April 2009 16:25
To: cf-talk
Subject: Re: YIKES! I must let internet users write SQL queries for our
database!
Robert Rawlins - Think Blue wrote:
Hey Ian,
My first thoughts on this would be to ensure that YOU keep total control
over the actually SQL that is being
-Original Message-
From: Ian Skinner [mailto:h...@ilsweb.com]
Sent: 23 April 2009 16:51
To: cf-talk
Subject: Re: YIKES! I must let internet users write SQL queries for our
database!
Robert Rawlins - Think Blue wrote:
Ian,
Just out of interest, how much data are we talking about
Ian Skinner wrote:
Did I get your attention? Luckily these are read-only queries, but still!
I forgot to mention an important consideration is to somehow control and
mitigate query requests so that users don't tie up the database with a
task taking hours and hours to process.
It is
Database tuning is an important line item on my discussion list for this
meeting.
To expand on some of your points.
First the system currently limits users to only selecting data from on
year at a time as a stop-gap measure to try and limit the operating cost
of the query. The trouble is
?
Rob
-Original Message-
From: s. isaac dealey [mailto:i...@turnkey.to]
Sent: 23 April 2009 17:27
To: cf-talk
Subject: Re: YIKES! I must let internet users write SQL queries for our
database!
Ian Skinner wrote:
Did I get your attention? Luckily these are read-only queries, but
still
s. isaac dealey wrote:
If CF is handling the database access you can set a timeout on the query
to prevent it from tying up the server?
CF is not handling the query. It is simply the interface to build the
query which then is submitted to the database. Stored procedures then
run the
and things like that to further extend
the performance of the system.
Rob
-Original Message-
From: Ian Skinner [mailto:h...@ilsweb.com]
Sent: 23 April 2009 17:35
To: cf-talk
Subject: Re: YIKES! I must let internet users write SQL queries for our
database!
Database tuning is an important
Yeah, the three main ideas I have developed so far are 1) database
tuning, 2) API/Web service 3)Possible go to Flex after the first two.
I agree that we are living with some unnecessary complexity. A good
deal of this process was developed in the 90s when databases and servers
were not
queries and tune the system to
perform sweetly for you.
Keep us posted on the progress you make, I'm sure I'll learn just as much
from it as you do.
Rob
-Original Message-
From: Ian Skinner [mailto:h...@ilsweb.com]
Sent: 23 April 2009 18:12
To: cf-talk
Subject: Re: YIKES! I must let internet
I wouldn't do it. The reasons are obvious. I would find out specifically
what objects / methods they are wanting to allow access to, and I would
build an API to give access only to those objects / methods. Open it up as a
web service API and do it right.
--
Jim Rising
Serial Entrepreneur
sorry guys... I guess I'm a bit late in the conversation, and my thread only
showed the initial post. :)
--
Jim Rising
Serial Entrepreneur
Software Engineer
Web Developer
Knowledge work requires both autonomy and accountability.
On Thu, Apr 23, 2009 at 6:57 PM, Jim Rising
19 matches
Mail list logo