Re: [sqlite] thoughts on a web-based front end to sqlite3 db?
On Fri, Mar 11, 2005 at 02:16:35PM -, Steve O'Hara wrote: > I'd like England to win the World Cup... I thought England did win the rugby World Cup the last time out? Oh, you mean _football_! ;-) -- Ng Pheng Siong <[EMAIL PROTECTED]> http://sandbox.rulemaker.net/ngps -+- M2Crypto, ZServerSSL for Zope, Blog http://www.sqlcrypt.com -+- Database Engine with Transparent AES Encryption
RE: [sqlite] thoughts on a web-based front end to sqlite3 db?
For what it's worth, if your in a hurry, try our product, it's Free. Basically, you launch our product, connect to your database and we'll spit out fully functional VB.NET or C# data/business entities using your database meta-data as the input. These objects (classes) do mostly everything that you need to do in a typical application. The advice below is good, and I would add one thing. How long will it (the application) be around and how hard will it be to maintain. anyway, see http://www.mygenerationsoftware.com if you're interested. - Mike > Here's my tuppence worth. > > I come from an engineering background where you're taught that rigour is > the > most important feature of any development. I find that all the > interpreted > environments tend not to be that great in this regard. Also, I don't have > an axe to grind when it comes to the "anything but Microsoft" prejudice > that > a lot of non-MS programmers seem to have. So, I would say that you need > to > decide what it is you're actually developing and then select a tool that > is > going to achieve that result - here's some questions to ask yourself; > > a) Am I developing a web application or just providing some dynmic > content > > b) Can I fix the deployment platform (Windows/Linux/Solaris) > > c) How much time have I got to develop this > > d) What level/quality of service do I need to provide > > There are lots of other questions but these are good ones to try and > resolve > straight off. > > Most of the applications I am involved in writing are multi-developer, > corporate wide systems and as such, it's not practical to choose a toolset > that isn't supported by a good vendor and a large user base. This tends > to > narrow the choices down to commercial products like > .NET/Java/Delphi/C/C++/VB - by commerical I'm talking about the > Development > Environments (IDE). > > Over the years I've come to realise that programming is much the same in > any > modern environment - same symantics, different syntax. what really makes > the difference for me is the development environment, I'm at the age where > I > can no longer bear the thought of using notepad/emacs/vi/vim as my > development editor for the sake of spending a few quid on a proper tool > for > the job that has Intellisense, aut-formatting, syntax checking etc. > > With that in mind, your choice is further narrowed and my current absolute > favourite is Java Servlets with JDBC using JetBrains IntelliJ. Low cost, > professional, high performance, good CV fodder, beautiful IDE. > If your pockets are deeper and you're sticking with Windows then .NET and > ADO is quite frankly the best possible way to go. > > Hey, you wanted an opinion > > p.s. anyone using assembler in a web environment should be kept away from > sharp objects for their own safety!! > > > > > -Original Message- > From: Eli Burke [mailto:[EMAIL PROTECTED] > Sent: 07 March 2005 21:23 > To: sqlite-users@sqlite.org > Subject: [sqlite] thoughts on a web-based front end to sqlite3 db? > > > I've been working on a project using sqlite3 since last fall. At the time, > I knew that it would need a web-based front-end eventually. I have a very > small bit of experience with PHP, and I assumed that PHP would support > sqlite3 sooner or later. Well, it's later, and as far as I know, PHP > is still using the 2.x branch. > > So, I was wondering if any of the more opinionated among you would care > to suggest an interface language. It'll be on a Linux box, presumably > running apache although I'm open to alternatives. The app itself uses > sqlite3 for scheduling jobs and storing job data, so the web interface > only needs to be able to insert some data and do visualization > (pretty standard stuff I think). > > Ease of learning is a plus as I need to get something basic up and > running fairly fast. I've heard good things about Python in that respect. > Does anyone have alternative suggestions, or if you agree that Python Is > Good, would you suggest using APSW, pysqlite, or something else? > > Thanks, > Eli > > > >
RE: [sqlite] thoughts on a web-based front end to sqlite3 db?
I'd like England to win the World Cup... Perhaps we can do a swap. -Original Message- From: Dinsmore, Jeff [mailto:[EMAIL PROTECTED] Sent: 08 March 2005 13:58 To: sqlite-users@sqlite.org Subject: RE: [sqlite] thoughts on a web-based front end to sqlite3 db? I personally would prefer replies that don't contain vulgar/obscene content. Thanks. Jeff Dinsmore MIS - Interfaces Ridgeview Medical Center [EMAIL PROTECTED] 952.442.2191 x6592 -Original Message- From: Richard Heyes [mailto:[EMAIL PROTECTED] Sent: Monday, March 07, 2005 8:37 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] thoughts on a web-based front end to sqlite3 db? Eli Burke wrote: > I've been working on a project using sqlite3 since last fall. At the > time, I knew that it would need a web-based front-end eventually. I > have a very small bit of experience with PHP, and I assumed that PHP > would support sqlite3 sooner or later. Well, it's later, and as far as > I know, PHP is still using the 2.x branch. > > So, I was wondering if any of the more opinionated among you would > care to suggest an interface language. It'll be on a Linux box, > presumably running apache although I'm open to alternatives. The app > itself uses sqlite3 for scheduling jobs and storing job data, so the > web interface only needs to be able to insert some data and do > visualization (pretty standard stuff I think). > > Ease of learning is a plus as I need to get something basic up and > running fairly fast. I've heard good things about Python in that respect. > Does anyone have alternative suggestions, or if you agree that Python Is > Good, would you suggest using APSW, pysqlite, or something else? Since noone has mentioned it yet, I'd suggest Brainfuck (http://www.muppetlabs.com/~breadbox/bf/). Very easy to learn (only eight instructions) so you should have something up and running pretty quickly. Notably, it has some of the most elegant code structure I've ever seen. HTH. -- Richard Heyes Ridgeview Medical Center Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
RE: [sqlite] thoughts on a web-based front end to sqlite3 db?
Here's my tuppence worth. I come from an engineering background where you're taught that rigour is the most important feature of any development. I find that all the interpreted environments tend not to be that great in this regard. Also, I don't have an axe to grind when it comes to the "anything but Microsoft" prejudice that a lot of non-MS programmers seem to have. So, I would say that you need to decide what it is you're actually developing and then select a tool that is going to achieve that result - here's some questions to ask yourself; a) Am I developing a web application or just providing some dynmic content b) Can I fix the deployment platform (Windows/Linux/Solaris) c) How much time have I got to develop this d) What level/quality of service do I need to provide There are lots of other questions but these are good ones to try and resolve straight off. Most of the applications I am involved in writing are multi-developer, corporate wide systems and as such, it's not practical to choose a toolset that isn't supported by a good vendor and a large user base. This tends to narrow the choices down to commercial products like .NET/Java/Delphi/C/C++/VB - by commerical I'm talking about the Development Environments (IDE). Over the years I've come to realise that programming is much the same in any modern environment - same symantics, different syntax. what really makes the difference for me is the development environment, I'm at the age where I can no longer bear the thought of using notepad/emacs/vi/vim as my development editor for the sake of spending a few quid on a proper tool for the job that has Intellisense, aut-formatting, syntax checking etc. With that in mind, your choice is further narrowed and my current absolute favourite is Java Servlets with JDBC using JetBrains IntelliJ. Low cost, professional, high performance, good CV fodder, beautiful IDE. If your pockets are deeper and you're sticking with Windows then .NET and ADO is quite frankly the best possible way to go. Hey, you wanted an opinion p.s. anyone using assembler in a web environment should be kept away from sharp objects for their own safety!! -Original Message- From: Eli Burke [mailto:[EMAIL PROTECTED] Sent: 07 March 2005 21:23 To: sqlite-users@sqlite.org Subject: [sqlite] thoughts on a web-based front end to sqlite3 db? I've been working on a project using sqlite3 since last fall. At the time, I knew that it would need a web-based front-end eventually. I have a very small bit of experience with PHP, and I assumed that PHP would support sqlite3 sooner or later. Well, it's later, and as far as I know, PHP is still using the 2.x branch. So, I was wondering if any of the more opinionated among you would care to suggest an interface language. It'll be on a Linux box, presumably running apache although I'm open to alternatives. The app itself uses sqlite3 for scheduling jobs and storing job data, so the web interface only needs to be able to insert some data and do visualization (pretty standard stuff I think). Ease of learning is a plus as I need to get something basic up and running fairly fast. I've heard good things about Python in that respect. Does anyone have alternative suggestions, or if you agree that Python Is Good, would you suggest using APSW, pysqlite, or something else? Thanks, Eli
Re: [sqlite] thoughts on a web-based front end to sqlite3 db?
Richard Heyes wrote: Since noone has mentioned it yet, I'd suggest Brainfuck (http://www.muppetlabs.com/~breadbox/bf/). Very easy to learn (only eight instructions) so you should have something up and running pretty quickly. Notably, it has some of the most elegant code structure I've ever seen. I know this is a little off topic, but anyone who finds BF interesting might also want to consider one of my personal favorites, Whitespace. You can get additional information at http://compsoc.dur.ac.uk/whitespace/. Have fun.
Re: [sqlite] thoughts on a web-based front end to sqlite3 db?
> Ease of learning is a plus as I need to get > something basic up and > running fairly fast. I've heard good things about > Python in that respect. > Does anyone have alternative suggestions, or if you > agree that Python Is > Good, would you suggest using APSW, pysqlite, or > something else? Do not underestimate the power of the SQLite console (aka the sqlite3 binary). I've been using php with sqlite module compiled in and perl with DBD::SQLite for long time. but after I wrote a simple 55lines SQL_direct parser for the console, I prefer using it. it gives me full access to all the .commands and input/output blobs via tempfiles. I just build up a file of SQLite commands and SQL queries to be executed and just parse it through like in: $textoutput= `$sqlite $database < $sqlcommandfile`; Blobs are handled via files. -- MortenB
Re: [sqlite] thoughts on a web-based front end to sqlite3 db?
On Tue, 8 Mar 2005 09:17:40 -0500 (EST), Clay Dowling <[EMAIL PROTECTED]> wrote: > > So, I was wondering if any of the more opinionated among you would care > > to suggest an interface language. It'll be on a Linux box, presumably > > running apache although I'm open to alternatives. The app itself uses > > sqlite3 for scheduling jobs and storing job data, so the web interface > > only needs to be able to insert some data and do visualization > > (pretty standard stuff I think). > > See this month's Linux journal for my opinions on the matter of interface > languages. SQLite3 is a dream to work with in a C++ CGI program, > especially true if you make use of my web template library > (http://www.lazarusid.com/libtemplate.shtml). > > Python is probably fine as well, as long as you aren't concerned about > performance. Bah, this is a red herring. I've built Python sites that handle millions of hits a day on top of Zope, and Zope isn't that efficient. There's sites running SkunkWeb that handle tons of load, and we're not talking about anything close to that here. Algorithms are 99% of the problem, language performance is 1%. People often blame the language (Python, Perl, Tcl, etc) for their own inability to understand algorithm behavior. O(N^2) is gonna suck on every platform, even if written in assembly when N becomes some reasonable number. Use what you're comfortable writing in, because that's what you'll be productive in. If that's C++ great, but don't not use a language because of performance concerns unless you truly have a C10K problem. Chris -- | Christopher Petrilli | [EMAIL PROTECTED]
Re: [sqlite] thoughts on a web-based front end to sqlite3 db?
[EMAIL PROTECTED] (Eli Burke) writes: > I've been working on a project using sqlite3 since last fall. At the time, > I knew that it would need a web-based front-end eventually. I have a very > small bit of experience with PHP, and I assumed that PHP would support > sqlite3 sooner or later. Well, it's later, and as far as I know, PHP > is still using the 2.x branch. sqlite3 is available in PHP through PDO: http://www.php.net/manual/en/ref.pdo.php Derrell
Re: [sqlite] thoughts on a web-based front end to sqlite3 db?
Eli Burke said: > So, I was wondering if any of the more opinionated among you would care > to suggest an interface language. It'll be on a Linux box, presumably > running apache although I'm open to alternatives. The app itself uses > sqlite3 for scheduling jobs and storing job data, so the web interface > only needs to be able to insert some data and do visualization > (pretty standard stuff I think). See this month's Linux journal for my opinions on the matter of interface languages. SQLite3 is a dream to work with in a C++ CGI program, especially true if you make use of my web template library (http://www.lazarusid.com/libtemplate.shtml). Python is probably fine as well, as long as you aren't concerned about performance. Clay -- Lazarus Notes from Lazarus Internet Development http://www.lazarusid.com/notes/ Articles, Reviews and Commentary on web development
Re: [sqlite] thoughts on a web-based front end to sqlite3 db?
Tcl is really fine for web interfaces. Porting an almost 10 year old web application to sqlite2 and sqlite3 was a charme. It is supporting Linux, SunOS,Windows and maybe HP-UX so far. If you are interested in an generic example using SQLite 3.1.3 (but also supporting 2.1.16) look at http://softguard.dyndns.org:8015 or https://softguard.dyndns.org:8016 user is 'testIt' (uppercase i) password is '$4SBS' for unlimited access. Please clean up any changes you make after testing. As SQLite needs no further administration creating databases and tables on the fly is as simple as using the command line. You only need a standard tcl distribution, tclhttpd3.5.1 and sqlite/tclsqlite itself to run it. PS.: This site is only for demonstration and in work. Internationalization does only support English and German. Also cloning and copying records does not work so far. The API is still limited and mostly directed to msql2/3. Andrew Piskorski wrote: On Mon, Mar 07, 2005 at 04:22:50PM -0500, Eli Burke wrote: I qualify as opinionated, so: Tcl. The fact that Dr. Hipp supports Tcl directly for SQLite is yet another bonus. running apache although I'm open to alternatives. The app itself uses AOLserver. Among other things, it goes very nicely with Tcl.
Re: [sqlite] thoughts on a web-based front end to sqlite3 db?
APSW is not DBAPI compliant but it's close enough Note that I do document how APSW differs from DBAPI. http://www.rogerbinns.com/apsw.html#dbapinotes APSW is very nice. Thanks :-) I've used it and PySQLite and I'd recommend APSW. It's "thinner". Note that it is almost impossible to do a DBAPI compliant interface to SQLite. For example DBAPI requires providing time types which SQLite doesn't natively provide. A wrapper has to "fake" it. Similarly various transaction methods must be provided (commit, rollback etc) which are almost impossible to implement without sniffing the SQL. Also don't kid yourself about how easy it is to move from one DBAPI compliant system to another. Pretty much all projects provide their own layer as glue between their code and the DBAPI drivers. If you want DBAPI compliance then use pysqlite. It tries really hard to fill in the necessary pieces that SQLite doesn't have. On the other hand if you only want to use SQLite then use APSW. It doesn't hide anything and gives you full access to all SQLite functionality. You can also do things like define your own collations and functions in Python. Where applicable APSW does use DBAPI conventions and names. As for a web front end, I suggest you make an XML-RPC wrapper around your database and then access that from whatever you want to use for your web stuff. As an example of something I worked on in the past, I implemented a PHP front end using Smarty templates and a Python process on the backend which was talked at using XML-RPC. The Python process did everything including managing sessions and storing the templates. The PHP/Smarty code dealt with display. This let me use each environment for what they were best at and decoupled them. I could also have done other front ends such as a command line, which comes in really handy if you need to automate some processes. Roger
Re: [sqlite] thoughts on a web-based front end to sqlite3 db?
Eli, I'd highly recommend Python. I've used Perl, PHP and Python. Python is hands-down the winner. After getting ahold of the elegance of Python, PHP feels like a hack job. Perl is "executable line noise". Python is very mature and very nice. It has a far cleaner implementation of just about everything, especially OO than Perl and _way_ better than PHP. I would also avoid Microsoft specific technology like the plague. APSW is not DBAPI compliant but it's close enough that migrating to a bigger database (PostgreSQL, _not_ MySQL!) would not be difficult at all. APSW is very nice. I've used it and PySQLite and I'd recommend APSW. It's "thinner". You should look at www.cherrypy.org for a nice little web server written in Python to get you going. It's really slick. Check out Snakelets also (http://snakelets.sourceforge.net). I prefer CherryPy because Snakelets has a templating language that is too-closely bound to the web server. CherryPy 2.0 (beta currently but works well) unbound the templating language for the 2.0 release so you can use your own. I built my own templating language because I couldn't find one that I like out there. With Python you do have a LOT to choose from so it can be daunting. If you have experience with PHP then you've learned how to embed source code in HTML. This is not a very good idea. Separation of the logic and the presentation make for a cleaner design in my opinion. Some would debate this but it's Ok if they're wrong! :) I'll be happy to chat with you. You can find me on Jabber at [EMAIL PROTECTED] Cordially, Scott On Monday 07 March 2005 01:22 pm, Eli Burke wrote: > I've been working on a project using sqlite3 since last fall. At the time, > I knew that it would need a web-based front-end eventually. I have a very > small bit of experience with PHP, and I assumed that PHP would support > sqlite3 sooner or later. Well, it's later, and as far as I know, PHP > is still using the 2.x branch. > > So, I was wondering if any of the more opinionated among you would care > to suggest an interface language. It'll be on a Linux box, presumably > running apache although I'm open to alternatives. The app itself uses > sqlite3 for scheduling jobs and storing job data, so the web interface > only needs to be able to insert some data and do visualization > (pretty standard stuff I think). > > Ease of learning is a plus as I need to get something basic up and > running fairly fast. I've heard good things about Python in that respect. > Does anyone have alternative suggestions, or if you agree that Python Is > Good, would you suggest using APSW, pysqlite, or something else? > > Thanks, > Eli
Re: [sqlite] thoughts on a web-based front end to sqlite3 db?
On Mon, Mar 07, 2005 at 04:22:50PM -0500, Eli Burke wrote: > Ease of learning is a plus as I need to get something basic up and > running fairly fast. I've heard good things about Python in that respect. > Does anyone have alternative suggestions, or if you agree that Python Is > Good, would you suggest using APSW, pysqlite, or something else? Python is not bad, and you only have APSW and pysqlite to choose from. OTOH, the number of web frameworks in/for Python probably rivals the number of available Linux distros... http://www.python.org/moin/WebProgramming http://www.python.org/moin/WebStack HTH. -- Ng Pheng Siong <[EMAIL PROTECTED]> http://sandbox.rulemaker.net/ngps -+- M2Crypto, ZServerSSL for Zope, Blog http://www.sqlcrypt.com -+- Database Engine with Transparent AES Encryption
Re: [sqlite] thoughts on a web-based front end to sqlite3 db?
Eli Burke wrote: I've been working on a project using sqlite3 since last fall. At the time, I knew that it would need a web-based front-end eventually. I have a very small bit of experience with PHP, and I assumed that PHP would support sqlite3 sooner or later. Well, it's later, and as far as I know, PHP is still using the 2.x branch. So, I was wondering if any of the more opinionated among you would care to suggest an interface language. It'll be on a Linux box, presumably running apache although I'm open to alternatives. The app itself uses sqlite3 for scheduling jobs and storing job data, so the web interface only needs to be able to insert some data and do visualization (pretty standard stuff I think). Ease of learning is a plus as I need to get something basic up and running fairly fast. I've heard good things about Python in that respect. Does anyone have alternative suggestions, or if you agree that Python Is Good, would you suggest using APSW, pysqlite, or something else? Since noone has mentioned it yet, I'd suggest Brainfuck (http://www.muppetlabs.com/~breadbox/bf/). Very easy to learn (only eight instructions) so you should have something up and running pretty quickly. Notably, it has some of the most elegant code structure I've ever seen. HTH. -- Richard Heyes
Re: [sqlite] thoughts on a web-based front end to sqlite3 db?
On Mon, Mar 07, 2005 at 04:22:50PM -0500, Eli Burke wrote: > So, I was wondering if any of the more opinionated among you would care > to suggest an interface language. It'll be on a Linux box, presumably I qualify as opinionated, so: Tcl. The fact that Dr. Hipp supports Tcl directly for SQLite is yet another bonus. > running apache although I'm open to alternatives. The app itself uses AOLserver. Among other things, it goes very nicely with Tcl. > Does anyone have alternative suggestions, or if you agree that Python Is > Good, would you suggest using APSW, pysqlite, or something else? People I trust are of the opinion that Python is a Good Thing, but I know nothing about one of its db APIs vs. another. -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com/
Re: [sqlite] thoughts on a web-based front end to sqlite3 db?
I strongly suggest to use pysqlite. APSW may be more powerfull in some areas but is not complaint with the python standard DB access API. If you will use pysqlite: 1) you will learn Python standard DBAPI 2) you will able to easly (relativly) migrate to another DB engine in future (mysql, postgresql, oracle...). Best regards, Witold Ease of learning is a plus as I need to get something basic up and running fairly fast. I've heard good things about Python in that respect. Does anyone have alternative suggestions, or if you agree that Python Is Good, would you suggest using APSW, pysqlite, or something else? Thanks, Eli
Re: [sqlite] thoughts on a web-based front end to sqlite3 db?
I suggest using a Perl 5.8 based solution. Perl is very mature and has strong SQLite 3 support in its extensions (DBD::SQLite). This will run on anything. It also isn't dependent on Microsoft technology. There are a number of pre-existing solutions on CPAN and elsewhere that you can look at for ideas, or for customizing. -- Darren Duncan At 4:22 PM -0500 3/7/05, Eli Burke wrote: I've been working on a project using sqlite3 since last fall. At the time, I knew that it would need a web-based front-end eventually. I have a very small bit of experience with PHP, and I assumed that PHP would support sqlite3 sooner or later. Well, it's later, and as far as I know, PHP is still using the 2.x branch. So, I was wondering if any of the more opinionated among you would care to suggest an interface language. It'll be on a Linux box, presumably running apache although I'm open to alternatives. The app itself uses sqlite3 for scheduling jobs and storing job data, so the web interface only needs to be able to insert some data and do visualization (pretty standard stuff I think). Ease of learning is a plus as I need to get something basic up and running fairly fast. I've heard good things about Python in that respect. Does anyone have alternative suggestions, or if you agree that Python Is Good, would you suggest using APSW, pysqlite, or something else? Thanks, Eli
[sqlite] thoughts on a web-based front end to sqlite3 db?
I've been working on a project using sqlite3 since last fall. At the time, I knew that it would need a web-based front-end eventually. I have a very small bit of experience with PHP, and I assumed that PHP would support sqlite3 sooner or later. Well, it's later, and as far as I know, PHP is still using the 2.x branch. So, I was wondering if any of the more opinionated among you would care to suggest an interface language. It'll be on a Linux box, presumably running apache although I'm open to alternatives. The app itself uses sqlite3 for scheduling jobs and storing job data, so the web interface only needs to be able to insert some data and do visualization (pretty standard stuff I think). Ease of learning is a plus as I need to get something basic up and running fairly fast. I've heard good things about Python in that respect. Does anyone have alternative suggestions, or if you agree that Python Is Good, would you suggest using APSW, pysqlite, or something else? Thanks, Eli
