Re: [sqlite] Copying Records from one table to another
From: "John Elrick"... jose isaias cabrera wrote: Greetings. I searched the mail archive and I can not find something related to this. I know it is easy, but... What I need is to copy a record from one Table1 to Table2 of the same DB. I tried, insert into LSOpenJobs select * where id = 530 from LSOpenSubProjects; Did you perhaps mean: insert into LSOpenJobs select * from LSOpenSubProjects where id = 530 ; ? Yep. that did it. Gracias. josé - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Request for help with the SQLite Website
At 1:40 AM + 11/14/07, [EMAIL PROTECTED] wrote: The new look for the SQLite website is now in place, if you haven't already noticed: http://www.sqlite.org/ The feedback from this mailing list has so far been very helpful. Please don't stop offering suggestions. So I just looked at the current website right now, and the main page and other pages look very good from what I can tell. Considerable improvements from the older website. Now, a few points on terminology that may seem minor to others, but not to me: 1. It is good that your main documentation is refering to SQLite as a "SQL DBMS" or "SQL engine" rather than using the word "relational" or "RDBMS" to describe it. The SQL standard doesn't call SQL "relational" and neither do other people who know what the relational model of data actually is, so I'm happy to see that the SQLite website seems to follow technical accuracy in this regard. 2. However, a different point needs adjusting in a few places, the term "database". A "database" is a managed collection of data, and it is *not* a program or program code. The website refers to SQLite being a "database" in a few places, but that is not true. Other places correctly call it a "database engine" or "database management system" or "DBMS", and that is correct; the other references should be fixed to say "database engine" or such when referring to SQLite itself. Only use the straight word "database" to refer to the data files or data file collections or RAM stores et al that store data managed by SQLite. Here are specific places on the front page that need the update, and are probably typos: * Unlike most other SQL databases, SQLite does not have a separate server process. Actually, that's the only such typo I found on the front page (should change to "SQL database engines"); all other occurrances of "database" looked correct, also great news. But this is something to keep in mind for the future if necessary. Keep up the good work. -- Darren Duncan P.S. I just noticed now that the 3.5.x line is now considered stable, which shows how much I was paying attention to some news details before ... thought it was still alpha. Now hopefully DBD::SQLite for Perl will be updated to include it sometime soon. - To unsubscribe, send email to [EMAIL PROTECTED] -
[sqlite] Copying Records from one table to another
Greetings. I searched the mail archive and I can not find something related to this. I know it is easy, but... What I need is to copy a record from one Table1 to Table2 of the same DB. I tried, insert into LSOpenJobs select * where id = 530 from LSOpenSubProjects; I would like to copy the whole record. Any help would be greatly appreciated. thanks, josé - To unsubscribe, send email to [EMAIL PROTECTED] -
RE: [sqlite] Suggests for improving the SQLite website
Just visited the new front page. I like it a lot. But one of the crown jewel features (at least to me) is buried in the fine print: Virtual Tables. Is this an oversight? I would at least put a blurb on the Features or Distinctive Features page unless there's a motivation not to do so (because it's experimental interface?). Just my 2c. Mark - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Copying Records from one table to another
jose isaias cabrera wrote: Greetings. I searched the mail archive and I can not find something related to this. I know it is easy, but... What I need is to copy a record from one Table1 to Table2 of the same DB. I tried, insert into LSOpenJobs select * where id = 530 from LSOpenSubProjects; Did you perhaps mean: insert into LSOpenJobs select * from LSOpenSubProjects where id = 530 ; ? John Elrick - To unsubscribe, send email to [EMAIL PROTECTED] -
RE: [sqlite] Request for help with the SQLite Website
Richard, I like the new website and layout, but find the initial page much to wordy for an initial screen. Just a suggestion: Create lots of white space to the left of the Current Status/Common Links box and leave the exiting paragraphs, but move them down visually Something like the following: [Title block] [menu bar] Home Sitemap Documentation Download License News Developers Support WHAT IS SQLITE?[ Existing Box Stays the same] o A SQL database engine o Self-contained, so it can be embedded in your program o Runs on more platforms than you can count on both hands o Widely used o Supported o Reliable o Simple without being simplistic o Free Small, Fast, Reliable. Choose any three! Now for the technical details:[Existing right hand box ends here] SQLite is a in-process library that . . . SQLite is an embedded SQL database engine.. SQLite is a compact library. ... SQLite has a reputation for being very reliable. ... The SQLite code base is ... We the developers hope ... Regards, Noah Hart CONFIDENTIALITY NOTICE: This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Suggests for improving the SQLite website
The latest sqlite page renders nicely on a wide screen and loads in 860mS on my machine and transfers a total of 16KB. It looks clean, terse, uncluttered and business-like and free of trivia. Just the presentation I relish when searching for information. Direct and to the point. Several suggestions: o The images and static pages have a max-age of zero so they are not cached by a browser or a proxy cache. It would be faster for the frequent user if they had a time to live and lodged in cache. o The text could be improved by changing the format to be more incisive. A possible format would be the "fact/benefit" style - "more..." link> Whitespace used to emphasize each point. Such a format is more easily comprehended and may be rapidly scanned by a reader doing a feature search. As Will Rogers said "You have one chance to make a first impression". - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Suggests for improving the SQLite website
Some suggestions: Under the SQL Language page, Split the page "expressions" into two, one for the sql expressions and one for SQL functions. It was not immediately obvious what sql functions were supported nor where to find them. Spelling/Grammar Home Page: second to last paragraph The developers are continue to expand the capabilities of SQLite and enhance its reliability and performance while maintaining . HTH [EMAIL PROTECTED] wrote: Thanks, everybody, for the excellent feedback and suggestions for revising the SQLite website. Please keep the comments coming. Regarding the basic "look" of the site, we were considering using a style similar to the once found at ActiveState http://www.activestate.com/ However, as we started to prototype this, we wrote down a very simple CSS/Javascript-free template and after looking at it, thought that this template might actually be better. By being CSS and Javascript-free, the new design also stays closer to the minimalist spirit of SQLite. A rough prototype of what a revised website might look like can be seen at http://sqlite.hwaci.com/ Please note that there are a lot of non-working links in this demo - it is just concept demo. And nobody is especially happy with the content of the homepage. (Suggestions for what should appear on the homepage are welcomed.) We are also working on a more elaborate concept that involves lots of CSS and javascript, pulldown menus, graphics, after the style of http://www.activestate.com/. Depending on how it looks in the end, we might or might not put the second up for review later today or Monday. Please continue to provide feedback. -- D. Richard Hipp - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Request for help with the SQLite Website
James Dennett wrote: Dennis Cote wrote: Dr Gerard Hammond wrote: The first few words sound incorrect to me. Shouldn't it be. "SQLite is an in-process" and even then I don't know what 'in-process' actually means. I agree with this completely. I can't say I have ever heard the term in-process before. Perhaps it is database administrator jargon. I thought it common in the programming world. It's certainly not a DBA thing; DBAs tend *not* to work with in-process sytems, but rather with client/server systems. In any case, I don't think it adds anything to the first sentence. It would be at least as effective without that term thrown in. For those to whom the term has meaning, it adds something useful by making the embedded nature of SQLite very clear (without using the ambiguous term "embedded"). -- James There was a suggestion here that professional web page designers be used. That was not sensible since good web pages should be simple and straight forward and a capable software designer has all the necessary skills to create excellent web pages. The sensible suggestion is that a skilled communicator help with the descriptive text so that it's meaning is clear to all and it grasps the attention of the reader instead of confusing with jargon and other examples of poor style. - To unsubscribe, send email to [EMAIL PROTECTED] -
RE: [sqlite] Request for help with the SQLite Website
Dennis Cote wrote: > > Dr Gerard Hammond wrote: > > The first few words sound incorrect to me. > > > > Shouldn't it be. > > > > "SQLite is an in-process" > > > > and even then I don't know what 'in-process' actually means. > > > > > I agree with this completely. > > I can't say I have ever heard the term in-process before. Perhaps it is > database administrator jargon. I thought it common in the programming world. It's certainly not a DBA thing; DBAs tend *not* to work with in-process sytems, but rather with client/server systems. > In any case, I don't think it adds anything to the first sentence. It > would be at least as effective without that term thrown in. For those to whom the term has meaning, it adds something useful by making the embedded nature of SQLite very clear (without using the ambiguous term "embedded"). -- James - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Request for help with the SQLite Website
[EMAIL PROTECTED] wrote: Dennis Cote <[EMAIL PROTECTED]> wrote: 5) There is no link to the CVStrac home page on the navigation bar Developers Richard, OK. I see that now. When I saw the Developers link I thought it was a link to the bios and pictures etc. for you and the other developers that had been requested as an addition to the new website. I never even clicked it to see what was there (which is obvious now I guess). When I go to CVStrac it is generally to look for, or to enter, bug reports. I often use the timeline to keep myself appraised of changes that are happening to SQLite. I have used the CVS source browser functions, but only to get a URL link to a file of interest for a posting to the mailing list. In general I think the wiki would be better served if it was linked from the documentation page. Perhaps the link on the navigation bar should be changed to Bug Reports or Bug Tracker, but that does not convey the fact that CVStrac is also used for new feature requests. I'm not sure what a better alternative would be, but Developers seems ambiguous and nearly everyone that uses SQLite is a developer, so it doesn't really mark stuff of interest to a subgroup of developers that might visit the website. I'm concerned that users may come to the site to file a bug report, then fail to find the appropriate links, and therefore simply leave because it is too hard to get to the right page. I'm not sure if most would think to click a CVStrac link or a Developers link to do so. It seems to me there must be a better alternative, but I don't have a real good suggestion. Hopefully someone else will. Dennis Cote - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Request for help with the SQLite Website
Dr Gerard Hammond wrote: The first few words sound incorrect to me. Shouldn't it be. "SQLite is an in-process" and even then I don't know what 'in-process' actually means. I agree with this completely. I can't say I have ever heard the term in-process before. Perhaps it is database administrator jargon. In any case, I don't think it adds anything to the first sentence. It would be at least as effective without that term thrown in. In my mind, this is a simpler, and hence better, description of SQLite: SQLite is a library that implements a self-contained, serverless, zero-configuration, transactional SQL database engine. It already covers all the keys points in-process is supposed to mean. It is a library. It is self-contained and serverless. Dennis Cote - To unsubscribe, send email to [EMAIL PROTECTED] -
RE: [sqlite] Request for help with the SQLite Website
The vast majority of database engines run as separate services on a machine and clients communicate with them through a network protocol. SQLite runs in the same process as the host application either as a statically linked or a dynamically loaded library and shares memory space of the client. This provides for a large number of advantages when in-process db is appropriate such as vastly easier integration with he client and almost completely removal of need to marshal data around (certainly not across process boundaries). For example when running performance analysis of MS SQL server you usually look at both the time it takes to execute any given query as well as the time it takes to transfer the resulting data from server to client. Since SQLite is in-process, the transfer time is essentially zero. You're right about the grammatical error though.. should be "an in-process". The original proposed text on this list was "SQLite is a high-efficiency, in-process, transactional" but "high-efficiency" was dropped without changing "a" to "an". HTH, Sam --- We're Hiring! Seeking a passionate developer to join our team building Flex based products. Position is in the Washington D.C. metro area. If interested contact [EMAIL PROTECTED] -Original Message- From: Dr Gerard Hammond [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 14, 2007 10:33 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Request for help with the SQLite Website The first few words sound incorrect to me. Shouldn't it be. "SQLite is an in-process" and even then I don't know what 'in-process' actually means. - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] BLOB data performance?
Hi all, I don't want to drive anyone away from SQLite (don't think that I can anyway :-)) but a good solution for storing large amounts of data is HDF5. HTH -- ds 2007/11/15, Roger Binns <[EMAIL PROTECTED]>: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Asif Lodhi wrote: > > Interestingly, Microsoft's SourceSafe (at least VS-6.0) apparently > > uses file system > > It basically uses a whole bunch of directories and uses a scheme very > similar to RCS to store the versioning content. > > > while SVN uses Berkeley DB as I read once. > > SVN initially only had Berkeley DB and it drove people nuts. In > particular it used to keep getting wedged and required manual > administrator intervention to fix. See this and the two following > questions: > > http://subversion.tigris.org/faq.html#stuck-bdb-repos > > SVN added a filesystem based backend using a directory to store the > deltas for each revision and that is by far the most popular. > > The moral of the tale is to make sure your backend database library > never needs human attention. I always wondered why they didn't use > SQLite. > > Roger > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHO9QNmOOfHg372QQRAh5vAKC4zRw0Uwq7Og8aKNLrIWiIE0XpRgCfashV > LgC0Y4jomgU+o7SXh8xHE6M= > =cVgu > -END PGP SIGNATURE- > > > - > To unsubscribe, send email to [EMAIL PROTECTED] > > - > > -- What is the difference between mechanical engineers and civil engineers? Mechanical engineers build weapons civil engineers build targets.
Re: [sqlite] Request for help with the SQLite Website
I guess letting developers having opinions about the website is like to many chefs making a soup. Everyone have different opinions. I like the new design but have a small comment about the rounded corners in the menu. If there are rounded corners in the menu - the content below the menu should have the additional margin as the radius of the rounded corner. Like this: http://onnerby.se/~daniel/sqlite_example/ Best regards Daniel - To unsubscribe, send email to [EMAIL PROTECTED] -
