OpenEuphoria

Re: DB - Final Question

• Posted by leviathan at uswest.net Feb 09, 2001
• 404 views

Heya CK :)

> For my current project, I need a database (Eu or MySQL), front-end (Eu or
> ?), and web server (Eu or ?). Right now I'm focusing on the database and
> front-end. Here are my options:
> 
> 1. Eu database with Eu front-end
> 2. MySQL database with Eu front-end
> 3. MySQL database with xx front-end
> 

Any of the above works, honestly. Tho it'd take some real skill to use 
a Eu db/Eu frontend/Eu server, as you're inventing the wheel for Eu.

IMHO, I work with a MySQL db with Apache+modphp3, so i'm used 
to that. But it would be soooo killer to see EDS backend, Eu server, 
and Eu communications :) (And it'd put Eu as finally a viable option 
for mass database use)

> Concerns:
>     a. multi-threads - for multi-user access

How about this: Your program runs as a daemon/TSR, basically, 
and the server program shoves to the database software query + 
jobnum, and the jobnum would be used on the server-end, which 
would keep, perhaps, the IP of the requesting machine or however 
web server softwares keep track of clients. This would be done one-
at-a-time, as Eu can't multithread quite yet, but hopefully it'll find the 
results fast enough so that the need to multithread isn't so significant.

And this would require you to write your own frontend to your EDS 
backend, and your own apache mod too, perhaps. Or your own 
webserver software altogether, with just enough functionality for you 
to get use out of it :)

>     b. web serving

Roll your own. Roll your own...

>     c. scalability - for millions of records in multiple databases

EDS can do that, so says Rob :)

>     d. multi-platform capability - starting w/Linux but client might want a
> Windows version in future

Shouldn't be too hard, since all you need is cross-platform anyway. 
(You're not using ints or anything to go and poke around memory, 
its all file commands and stuff)

The only trouble I see? Winsock vs sockets... but perhaps one could 
make a unified library for both and use a bunch of "if platform = " to 
keep it all together.

> One of my thoughts is, I can start with a Eu DB and, when time to scale up,
> export the data to a MySQL DB.

If EDS can, in fact, scale to millions of records, i see no need to 
expand to a sql db...

Hope this helps a little,

--"LEVIATHAN"