; Subject: RE: OT: Design Question: Storing web pages in a database.
>
>
> Very cool - thanks =)
>
> Question for you... the next issue I'm addressing is that this
> system will work very easily for storage of straight html. Do
> you have any recommendations on how to
On Mon, Feb 14, 2000 at 11:07:35AM -0500, Gene wrote:
:
: > >
: > > Make sure you addslashes() before inserting into the blob fields, and
: > > stripslashes() when pulling back out of blobs.
:
: Hi,
:
: Are these functions built into mysql, or do I have to write them
: myself? If so, does anyon
> >
> > Make sure you addslashes() before inserting into the blob fields, and
> > stripslashes() when pulling back out of blobs.
Hi,
Are these functions built into mysql, or do I have to write them
myself? If so, does anyone have a reference implementation?
Thanks,
===
I personally prefer this approach too (or any variation on the theme). You
really don't want to mix content and layout (and sounds like this is the
problem you are trying to solve anyway), and the templates allow
global mods from one (or a few) places.
Obviously your content has to be suitable,
> Yes, but now updating the pages is harder than if they are on disk! Just a
> counter point.
>
> charles
Thanks for the counter point Charles =) The main benefit would be adding a
layer of abstraction for authors. All of the pages on the site are dynamic
and being created by pulling different
> I would prefer mysql /php3.
>
> Checkout the tutorial at www.webmonkey.com to build dynamic websites with
> mysql/php3.
>
> Looking forward to your feedback.
>
>
> Danny
Hi Danny =) I had read through the article. It covered the basics. That
was good enough to get me past the first hurdle o
Very cool - thanks =)
Question for you... the next issue I'm addressing is that this
system will work very easily for storage of straight html. Do
you have any recommendations on how to integrate graphics into
these documents?
-Ed
> Simple.. Two tables something like this (MySQL specific):
> Yes, but now updating the pages is harder than if they are on disk! Just a
> counter point.
I am in the process of writing a simple site (currently < 50 pages) and am
using php, mysql and fast template. The reason I like this is no one I work
with wants to update html code. I made a simple form
Although there are certainly benefits to doing this, I'd say make sure you
have a good reason for doing so, otherwise it's a lot of complexity for
little gain.
Perhaps if you explained what you are doing it a bit more detail we can
comment more. For just creating pages from multiple pieces, php a
I would prefer mysql /php3.
Checkout the tutorial at www.webmonkey.com to build dynamic websites with
mysql/php3.
Looking forward to your feedback.
Danny
dannyh
At 12:45 13/02/2000 -0500, Jason Costomiris wrote:
>On Sun, Feb 13, 2000 at 12:08:34AM -0800, Ed Lazor wrote:
>: Has anyone done t
On Sun, Feb 13, 2000 at 12:08:34AM -0800, Ed Lazor wrote:
: Has anyone done this? (or is this considered a bad thing?)
Done it before, would probably do it again. Not a bad thing at all,
at least from the standpoint of maintaining the site. You don't have to
deal with lots of files. Particula
No help but curious. Isn't a multi-page web document just a bigger html file?
Is there something special about these documents that I am missing?
Bret
Ed Lazor wrote:
> Has anyone done this? (or is this considered a bad thing?)
>
> If you have, could you give me some pointers on the design yo
Has anyone done this? (or is this considered a bad thing?)
If you have, could you give me some pointers on the design you used to store
and retrieve multi-page web documents using the database?
I've been able to store single page web files with no problem. I'm
designing something for multi-pag
13 matches
Mail list logo
