Web applications are nice. They’re useful, they’re cross-platform, users need no installation, no upgrades, no maintenance, not even the computing or storage power to which they are used. As weird as it may sound, I’ve even seen announcements for web applications supposed to run your games on distant high-end computers so that you can actually play on low-end computers. Go web application!

Of course, there are a few downsides to web applications. Firstly, they require a web connexion. Secondly, they are largely composed of plumbing. Finally, ensuring their security is a constant fight.

How many pipes do you need?

If you have ever developed a web application, you know what I mean by plumbing: just writing an online TODO list — the equivalent of maybe twenty minutes of work in Visual Basic, in Python, Java or Objective-C — requires mixing an insane amount of languages, to define your user interface (HTML, JavaScript, CSS), to define your storage (DDL, DML, DCL, plus possibly an ORM language), to get your server and your client to communicate (XML, more JavaScript, PHP or one of its competitors, as well as some HTTP and a little MIME configuration), to launch your application (whichever configuration languages are used by your server). Of course, if your application is a bit more complex and requires something like compatibility with smartphones, or like distant storage, or distributed computing, or backups, or modularity (in the world of the web, it’s called “web services”)… well, you will probably require a few additional languages.

All of this is just plumbing. Only once you have written it can you concentrate on the core of the application. And once the application is written, the pain is just starting, because chances are that your application can be attacked by hijacking the link between your user interface and the core (cross-site scripting) or between the core and the storage (SQL injection) or by keeping the user interface and replacing the application core (man-in-the-middle attacks) or by replacing the user interface by a malicious client or by taking the place of a currently connected user to steal some of its credentials (rebinding) or by taking advantage of low-level bugs (buffer over/underflows), etc.

None of this is a show-stopper, of course — just take a look at the web and you will see thousands of web applications. Just like the complexity of Software Development Kits in the early days of Windows, MacOS or X didn’t stop adventurous hackers from developing desktop applications. But of course, if twenty-five years of desktop application development have taught us one thing, it is that the life of developers can be made easier. Nowadays, a few generations of SDKs later, Windows developers have .Net, C# and Visual Studio, Macintosh developers have Cocoa, Objective-C and XCode, while X-based developers have the libraries of Gnome/KDE, Python and a variety of programming environments. The growing popularity (and libraries) of Haskell, F#, OCaml, Scala and other functional programming languages could mean that one of the next generations of SDKs will increase safety and security.

The web hasn’t quite reached that stage yet. Even the state-of-the-art in web frameworks only provides features slightly more advanced than early Windows/Mac/X SDKs: low-level bindings for low-level mechanisms, designed to ensure low-level properties. Or, rephrased differently, in the current state of web development, GMail, Google Maps or Facebook are still considered complicated applications, although they are conceptually quite simple and should therefore be equally simple to implement.

We can do better. How? By removing the need for plumbing. By providing automated mechanisms for ensuring high-level security properties. By providing language support for common patterns.

Enter OPA

Let me introduce OPA. OPA, or One Pot Application, is a complete development platform for web applications and web services. Development in OPA requires no plumbing. Applications developed with OPA are automatically checked for safety and security before they are executed. Applications developed with OPA are automatically (and provably) immune to cross-site scripting, to SQL injections and to most existing forms of attacks. And OPA provides language support for storage, communication between client and server (Ajax and Comet), concurrency, distribution, mobility, etc.

With OPA, we intend to skip several generations of SDKs and provide right now a high-level and modern programming platform. OPA has been 6 years in the making: 4 years of sketches, mockups and prototypes as part of academic research projects and 2 years of actual implementation at MLstate. A few days ago, OPA has officially entered demonstrable status. Not quite ready for prime time, but definitely usable for development. Do you want to write an online note-taking application? That’s about 20 lines of code, from scratch. A minimal chat? About 30 lines. A multi-channel, distributed chat? About 80 lines. A minesweeper? About 100. We’re using it to develop utilities, content management systems, tools for administrations and games.

Pre-alpha builds of OPA have been distributed to selected partners. A public version will be made available within a few weeks, as well as commercial applications developed with OPA. In the meantime, we are busy improving the syntax, completing the standard library, making error messages intelligible, fixing the bugs and extending the range of safety and security checks.

In the meantime, you can take a look at a video recorded during ICFP presenting OPA and MLstate.

Stay tuned.

Objective:
The aim of this write-up is to show how easy it is to create table in sqlite table in C. The  example below show how you can create/ open a DB file, create multiple table, Insert & retrieve records.

Getting Started:

Libraies you might require
libslqite3-development package
In ubuntu you could install it with the help of apt-get
CMD:    sudo apt-get install libsqlite3-dev

To view the Db file you can use sqlitebrowser
CMD: sudo apt-get install sqlitebrowser

Quick Summary:
a. Line 49 Show how to open/create a DB file
b. Line 65, 76 create new table UserMenu & SettingsMenu
c. Line 80-84 , 86-90 Show how to insert into the database.
d. Line 104-133 : Sow how to reteve the data
f. Line 136: Finaly, show how to close the DB.

Source

 /******************************************************************************
  *  To Compile:                                                               *
  *  !gcc -o sql_multitable_sample sql_multitable_sample.c  -Wall -W           *
  *                                 -O2 -Wl,-R/usr/local/lib -lsqlite3         *
  *  Create multiple tables in a file and adding new rows to the table.        *
  *  Added callback function for the sql exec function to handle the query     *
  *  results.                                                                  *
  ******************************************************************************/


 #include<stdio.h>
 #include<sqlite3.h>
 #include<stdlib.h>

 /* Callback called when the query is exceuted */
 static int callback(void *NotUsed, int argc, char **argv, char **azColName)
 {
 	printf ("\n ******** Inside Callback\n");
 	int i;
 	int rowpr=argc-1;
 	NotUsed=0;
 	printf("\n %s ",__FUNCTION__);
 	for(i=0; i<rowpr; i++)
 		printf("%s ",azColName[i]);

 	printf("%s\n",azColName[rowpr]);



 	for(i=0; i<rowpr; i++){
 		printf("%s ",  argv[i] ? argv[i] : "NULL");

 	}
 	printf("%s\n",  argv[rowpr] ? argv[rowpr] : "NULL");

 	return 0;
 }

 int main()
 {
 	//return value
 	int retval;

 	int q_cnt = 10,q_size = 150,ind = 0;
 	char **queries = malloc(sizeof(char) * q_cnt * q_size);
 	// Creating statment & opening new DB
 	sqlite3_stmt *stmt;
 	sqlite3 *handle;
 	retval = sqlite3_open("FirstDB.sqlite3",&handle);
 	if(retval)
 	{
 		// If connection failed, handle returns NULL
 		printf("Database connection failed\n");
 		return -1;
 	}
 	printf("Connection successful\n");

 	// creating a multilple tables
 	char create_table[] = "CREATE TABLE IF NOT EXISTS UsersMenu (uname TEXT PRIMARY KEY,pass TEXT NOT NULL,activated INTEGER)";
 	char create_table1[] = "CREATE TABLE IF NOT EXISTS SettingsMenu (app_id TEXT PRIMARY KEY,gconf_path TEXT NOT NULL,activated INTEGER)";


 	char *errmsg = NULL;
 	// Execute the query
 	retval = sqlite3_exec(handle,create_table1,callback,handle,&errmsg);
 	if(retval != SQLITE_OK)
 	{
 		if(errmsg != NULL)
 		{
 			printf("\n@@Exec err:%s\n",errmsg);
 			sqlite3_free(errmsg);
 		}

 	}
 	printf ("\n---> create_table1 retvalue %d %s \n",retval, sqlite3_errmsg(handle));
 	retval = sqlite3_exec(handle,create_table,callback,0,0);
 	retval = 0;
 	printf ("\n ---> create_table retvalue %d %s \n",retval, sqlite3_errmsg(handle) );

 	// now Insert rows into table UsersMenu
 	queries[ind++] = "INSERT INTO UsersMenu VALUES('Speaker','Creative',1)";
 	retval = sqlite3_exec(handle,queries[ind-1],callback,0,0);
 	queries[ind++] = "INSERT INTO UsersMenu VALUES('Mouse','Logitech',0)";
 	retval = sqlite3_exec(handle,queries[ind-1],callback,0,0);

 	// now Insert rows into table SettingsMenu
 	queries[ind++] = "INSERT INTO SettingsMenu VALUES('media_player','$HOME/media',1)";
 	retval = sqlite3_exec(handle,queries[ind-1],callback,0,0);
 	queries[ind++] = "INSERT INTO SettingsiMenu VALUES('picture_viewer','$HOME/pic',0)";
 	retval = sqlite3_exec(handle,queries[ind-1],callback,0,0);

 	// select query from the table
 	queries[ind++] = "SELECT * from UsersMenu";
 	retval = sqlite3_prepare_v2(handle,queries[ind-1],-1,&stmt,0);
 	if(retval)
 	{
 		printf("Selecting data from DB Failed\n");
 		return -1;
 	}

 	// Read the number of rows fetched
 	int cols = sqlite3_column_count(stmt);
 	int col =0;
 	while(1)
 	{
 		// fetch a row's status
 		retval = sqlite3_step(stmt);

 		if(retval == SQLITE_ROW)
 		{
 			// SQLITE_ROW means fetched a row

 			// sqlite3_column_text returns a const void* , typecast it to const char*
 			for( col=0 ; col<cols;col++)
 			{
 				const char *val = (const char*)sqlite3_column_text(stmt,col);
 				printf("%s = %s\t",sqlite3_column_name(stmt,col),val);
 			}
 			printf("\n");
 		}
 		else if(retval == SQLITE_DONE)
 		{
 			// All rows finished
 			printf("All rows fetched\n");
 			break;
 		}
 		else
 		{
 			// Some error encountered
 			printf("Some error encountered\n");
 			return -1;
 		}
 	}

 	// Close the handle to free memory
 	sqlite3_close(handle);
 	return 0;
 }

How to build & run
Issue the command build the source
CMD: gcc -o sql_multitable_sample sql_multitable_sample.c  -Wall -W -O2 -Wl,-R/usr/local/lib -lsqlite3
To run excecute ./sql_multitable_sample.

Output: A DB file FirstDB.sqlite3 will be create in the current directory.

Now, view  the DB file with SqliteBrowser
Issue CMD: sqlitebrowser FirstDB.sqlite3

Enjoy playing around with Sqlite …  it really nice!!

A new beta of QC 1.6, beta 4, is now available on sourceforge.  I has the following fixes and changes

1. DBScript can now be used with native databases.
2. All examples shipping in the download of the beta are now converted to the 1.6 file structure.  A few of the examples have not been ported yet and so I have not included them yet.  I’ll put them in the next beta.
3. ServerAccessObject timeout defect fixed that triggered multiple calls to VCO’s
4. Cleaned up DataAccessObject batch method (a support method for DBScript.  Don’t use it directly).  Simplified batch completion checking.
5. Fixed DataAccessObject transaction handling that caused transactions not to appear to fail if database constraints were violated.
6. SQLite updated to version 3.6.20 with support for FTS3 query syntax added
7. Added missing NativeFooter Example
8. Fixed failure to hide native footer defect
9. Added new JQTouch example showing the JQTouch developer demo

En la siguiente direccion linux +

podeis descargaros la revista linux +, en formato PDF. En el nº de 56, aparece un articulo dedicado al Acceso a Bases de Datos SQLITE, de Jorge Emanuel Capurro (paginas 72 a la 82)

Espero que os guste, un saludo

How many times you put your best effort in making a project only to be ridiculed during the presentation with words like “This is shit”.”WTF is this” by the teachers.  OK OK! I am exaggerating, but it is a truth that students who put their best don’t get their reward. Most of such students put their sincere effort just because they like their work and not just for marks. To add insult to injury, those who copy-paste the projects get great reviews.

The situation is no different in Computer Science branch too. We loose hundreds of such talents students just because they became de-moralized after poor feedback for their project by the faculty. They should realize that hard-work in college hardly pays off. They should put their coding efforts in competitions like “Google Code Jam”, “CodeChef” or some open-source projects.

Now the million dollar question is “How to handle the college projects”? Let me explain with an example.

Project: Create a source Control Management or Revision Control System for efficient code management for single person project.

Technology: Python with SQLite for client.

Additional Information: There need not be a central repo to push the changes, local commits are enough. The name of the binary should be srcs or “Simple Revision Control System“

Creating the Project:

In real world development, people would ask you to make tons of documents like SRS, Technical Specification etc before moving on to coding. These things simply don’t exist in colleges. All you need to do for your project to be ready is shown below.

You need to run the following commands on any Debian based distro (probably Ubuntu)

$ sudo apt-get install bzr

$ sudo ln -s /usr/bin/bzr /usr/bin/srcs

….. and it’s done. Now let’s start using it

Creating the repository

$ cd ~ && mkdir code && cd code

$ srcs init

Creating files

$ touch file1.c

$ touch README

Adding and committing

$ srcs add file1.c README

$ srcs commit file1.c README -m "First Commit"

So your project part is complete. Now come let’s handle the typical vivas

Conversation 1:

Teacher: Why have you used Python?

You: Python is _______________(put all sorts of Python advocacy here)__________________

Teacher: What. Explain it clearly!

You:  So that you can’t make the head or tail of the codebase.

Conversation 2:

Teacher: Explain your project briefly!

You: My project is to create a system to manage the code. Keep revisions, find the differences between two commits

Teacher: How to keep differences?

You: I save the code at regular intervals, or say commit it to the repo, so that I can access any file any time if I make a mistake

Teacher: Why the **** do you need to make such a big software to keep copies. Can’t you just use “Save As(s)” every time you need revision of a file?

You: *Facepalm*

Using shell to access sqlite

$ adb [-s <AVD name>] shell
# sqlite3 /data/data/<application package name>/databases/<database name>

Example:
>adb shell
$ sqlite3 /data/data/com.kroz.app/databases/mydatabase.db
sqlite3 /data/data/com.kroz.app/databases/mydatabase.db
SQLite version 3.5.9
Enter ".help" for instructions
sqlite>

Mais uma matéria muito interessante da PC World. Nela o autor sugere uma lista de dez softwares livres para gerenciamento do negócio, gerenciamento de conteúdo e fluxo de informações.

É bom lembrar que, por exemplo, um ERP é composto de aplicativos e bancos de dados. Quando a empresa investe num ERP comercial, ela necessita adequar a infraestrutura de TI adquirindo novos servidores, sistemas operacionais, gerenciadores de bancos de dados, os pacotes do ERP, as licenças de uso, horas de consultoria de implantação e treinamento. Com o software livre, as licenças de uso, os sistemas operacionais, os aplicativos e os bancos de dados podem ser abatidos do custo. Parte desse custo será direcionado para as horas de consultoria e treinamento. Entretanto, após esse investimento inicial, restará apenas as manutenções periódicas dos bancos de dados e do desenvolvimento de aplicativos customizados. As atualizações serão gratuitas e, você pode mudar de fornecedor quando quiser, se não estiver satisfeito com o seu.

Ao contrário de soluções proprietárias, se você mudar de fornecedor, terá de mudar todo o sistema, também.

Se você é empresário e está buscando uma solução efetiva sem obrigar sua empresa a depender de um único fornecedor nem de uma tecnologia, pesquise por empresas de suporte que façam a implantação de softwares de gestão em código aberto.

Leia a matéria em: http://pcworld.uol.com.br/dicas/2009/11/04/onze-softwares-gratuitos-para-cuidar-da-gestao-da-sua-empresa

Thanks to http://www.otterbook.com/blog/2009/08/fixing-the-sqlite-db-for-a-trac-instance/ , I found out how to fix a Trac instance when I got the message

“DatabaseError: database disk image is malformed”

Here it is:

$ cd /path/to/trac-sqlite-db-directory # find the trac.db file
$ su www-data   # switch to the owner of the db file
$ mv trac.db trac.db.damaged
$ sqlite3 trac.db.damaged .dump|sqlite3 trac.db

Read/Write data on the iPhone: Property Lists, SQLite, or Core Data? | Tapity.

Plists, SQLite, or Core Data…which is best for persistent data in my iPhone app?

QCiPhone 1.6 beta 3 includes:

• All new Xcode apps created using the 1.6 beta 2 or later Xcode template will auto-update to a new version of QCiPhone when you run the QCFamily installer
• A fix for the permission build error in beta 2
• In application maps.  This feature allows you to drop any number of pins as well as show the current location of the device.
• A new object, DBScript, that allows you to do bulk updates to the SQLite database in a transactionally safe fashion (in-browser only for now.  Will work for native databases in the next beta.

Examples for both the in-app maps (MapExample) and DBScript (BrowserDBScript) exist in the iPhone Examples directory of the download.

The post just previous to this one shows how to use the DBScript object.

I just added SQLite bulk updates for in-browser databases (native databases coming soon) to the QuickConnect iPhone framework (1.6 beta 3).  I did this by creating and adding to the framework an object called DBScript.  It is transactionally safe.  If one of your updates in the script fails all changes are rolled back.

It is also easy to use.  The code below comes from the databaseDefinition.js file of the new BrowserDBScript dashcode example.  In it a link to the database is established using the DataAccessObject.  Then the DBScript object is created and a series of SQL statements are added to the script.  Lastly, the script is executed.  Notice that the script object works for both standard and prepared statements.

If you are using this after a data pull from a network resource or after querying the user for information to insert, make sure you use a prepared statement type call to avoid SQL insertion attacks.

/*

* An example of how to use the DBScript object to populate a database.

* This will be done as a single transaction and is transactionally safe.

* This means that all changes will be rolled back if any

* database error happens.

*/

//create or connect to the in-UIWebView database

var database = new DataAccessObject(“WelcomeExample”, “1.0″, “Welcome example”, 20);

//create the script object

var bulkInsertScript = new DBScript(database);

//add all statements to the script object

bulkInsertScript.addStatement(“CREATE TABLE IF NOT EXISTS names (id INTEGER UNIQUE, name TEXT)”);

bulkInsertScript.addStatement(“INSERT INTO names VALUES(1,’Bob’)”);

bulkInsertScript.addStatement(“INSERT INTO names VALUES(2,’Sue’)”);

//and example of using a prepared statement

bulkInsertScript.addStatement(“INSERT INTO names VALUES(?,?)”,[3,"Jose"]);

bulkInsertScript.addStatement(“INSERT INTO names VALUES(4,’Bjorn’)”);

bulkInsertScript.addStatement(“INSERT INTO names VALUES(5,’Jean’)”);

bulkInsertScript.addStatement(“INSERT INTO names VALUES(6,’Gustav’)”);

//execute all statements within a transaction

bulkInsertScript.executeSetDataScript();

If we’re looking for duplicates inside the same table:

select (refLocation, macroName)
FROM macrosMD5
GROUP BY refLocation
HAVING( COUNT(refLocation)>1);;

In this case we’re looking for macros with the same refLocation

PHP код для проверки

<?php
$db = new SQLite3('test.db');
if(!is_file('test.db')) $db->exec("CREATE TABLE i_s (id INTEGER PRIMARY KEY AUTOINCREMENT,data TEXT)");

print_r($time);
?>

Общие сведения

Таблица    : CREATE TABLE i_s (id INTEGER PRIMARY KEY AUTOINCREMENT,data TEXT);
Запись    : INSERT INTO i_s (data) VALUES (‘”.microtime(1).”‘)

Типы тестирования

SQLite3::exec() -> без commit, 1000 строк на запись
59.185881853104 сек
SQLite3::exec() -> с commit, 1000 строк на запись
0.21351504325867 сек
SQLite3::query() -> без commit, 1000 строк на запись
56.950169086456
SQLite3::query() -> с commit, 1000 строк на запись
0.26426601409912

Тестируем запросы с commit, увеличив количество записей до 100 000

SQLite3::exec() -> с commit, 100 000 строк на запись
14.51909995079
SQLite3::query() -> с commit, 100 000 строк на запись
14.552824020386

Тестируем запросы с commit, увеличив количество записей до 100 000 000

SQLite3::exec() -> с commit, 100 000 000 строк на запись
не проверено
SQLite3::query() -> с commit, 100 000 000 строк на запись
не проверено

Замеченные детали

При использовании COMMIT идет нагрузка на процессор.
Если не использовать COMMIT то нагруска идет на жесткий диск.

We can use transactions, nothing really fancy

Actually, SQLite will easily do 50,000 or more INSERT statements per second on an average desktop computer. But it will only do a few dozen transactions per second. Transaction speed is limited by the rotational speed of your disk drive. A transaction normally requires two complete rotations of the disk platter, which on a 7200RPM disk drive limits you to about 60 transactions per second.Transaction speed is limited by disk drive speed because (by default) SQLite actually waits until the data really is safely stored on the disk surface before the transaction is complete. That way, if you suddenly lose power or if your OS crashes, your data is still safe. For details, read about atomic commit in SQLite..

Another solution is to set the synchronous pragma to false

ith synchronous OFF (0), SQLite continues without pausing as soon as it has handed data off to the operating system. If the application running SQLite crashes, the data will be safe, but the database might become corrupted if the operating system crashes or the computer loses power before that data has been written to the disk surface. On the other hand, some operations are as much as 50 or more times faster with synchronous OFF.

A idéia de abandonar o arquivo XML já vem me azucrinando a cabeça não é de hoje. Estudei um pouco só para fazer a implementação do driver SQLite dentro do Visual Studio, graças à um bom esforço da comunidade, hoje o SQLite fala com o Server Explorer do Visual Studio, isso ajuda muito no desenho e desenvolvimento das tabelas que serão empregadas.

Vou começar a guardar estados do cenário, como já comentei, com classes estáticas (por enquanto) estou guardando o estado de moedas, mas o mapa é algo complexo, pois se você visitar um determinado portal ou seja, entrar por exemplo na estação de água e voltar para o cenário existe algumas regras que devem ser seguidas.

O cenário já suporta mudanças de estado, isso ajuda bastante, mas ainda assim, existem mais coisas para se fazer. Por exemplo, se eu já abri um baú ele deve voltar ao cenário no estado aberto e não ter mais possibilidade de ser aberto (isso é estado do objeto e não do cenário).

Aqui está um pequeno (bem pequeno pra ser sincero) teste que fiz, ele vai possibilitar gerenciar os estados através de um tabela SQLite.

Eu me empolguei em falar do SQLite e esqueci de algo básico. Estou implementando marcadores de retorno (vide o “R” nas imagens), este objeto vai fazer que você volte automaticamente para um determinado ponto do jogo, e não mais apareça somente no posicionamento do WorldSpawn (o primeiro ponto de retorno que foi criado no jogo).

Neste exemplo, o P é o portal que vai te levar para o cenário da estação de água, já o R fará com que você ao sair do cenário da estação de água, retorno para o ponto mais próximo do portal.

Ainda precisa de ajustes, mas em breve deverá estar ok, aí sim, virá uma fase dificil realmente, que é migrar o XML para o SQLite, o processo hoje no XML é bom, mas via SQLite será bem melhor (não acredito que seja mais rápido, mas me abre mais possibilidades e me dará mais segurança).

Easy Databasing with SQLite | Build Internet!.

I have not given up on my quest to be able to generate reports on my Lightroom database catalog. I talked about my reasons for it here and here.

The imaginatively named SQLite Database Browser I found at sourceforge.net is very slow.

SQLite Database Browser About

But yesterday a poster to this blog recommended a better one. It’s called SQLite Spy. It’s free for non-commercial use. I like free! You can download it here.

SQLiteSpy About

It is very fast – even when examining my 1GB main Lightroom Catalog. (I am living in fear that it will break soon. I’m approaching 50,000 pictures catalogued. See here and here.)

Here’s the SQLiteSpy display of the table “Adobe_images” that has one row for every photo (or virtual copy) catalogued by Lightroom.

SQLiteSpy Adobe_images - click to see full sized

Of course, this is an extremely powerful tool. I must be very careful, especially with my “production” catalog. I read a cautionary tale here about how a Lightroom user / database geek made Lightroom behave very strangely by making a change to the database using SQL.

He deleted references to some sidecar files by replacing the contents of the field with NULL. But Lightroom started acting strangely and would not display thumbnails consistently. It turned out that he should have used an empty string rather than NULL.

That distinction is a classic database programming error but it is very obscure to most people. Try explaining the difference between NULL and an empty string to a child! Actually, I thought that using NULL was better programming practice as database are optimized for NULL checks. But the Adobe engineer who wrote that part of Lightroom used an empty string and never imagined that anybody would mess with her tables.

I should spend the time to reverse-engineer the Lightroom Catalog schema. That’s the database geek word for the tables and most importantly the relationships between them. But my database knowledge is rusty and it would take me weeks. Adobe will release Lightroom 3.0 before I’m satisfied.

Also …

The ability to execute arbitrary SQL on the database is useful and it may save me from some problems that cannot be fixed using the Lightroom client. Maybe there’s something wrong with the database that causes my “Ever Changing Status” problem. Every time Lightroom crashes I worry the catalog will be corrupted.

But – it isn’t what I want. I have yet to find a fully functional ODBC driver that will allow me to attach SQLite tables to Microsoft Access. Then I can do the database reports that I crave. There’s so much good information in my metadata but I cannot present it as I would like.

از نسخه فايرفاكس 3.0 به يعد بوكماركها ، هيستوري ، ليست دانلودها و اطلاعاتي از اين دست در ديتابيس هاي sqlite  ذخيره شدند كه مزايا و معايبي دارد به مرور زمان و با توجه به عادت وبگرديتان اين ديتابيس ها داراي اطلاعات مفيد و حجيمي خواهد شد مثلا نوار آدرس هوشمند فايرفاكس 3 با توجه به تعداد دفعات بازديد، عنوان و… پايگاه داده سايتهاي بازديد شده رو جستجو كرده و ليستي از آدرسها را پيشنهاد ميده كه اكثر اوقات بسيار مفيد است. فايرفاكس حدود ده ديتابيس SQLite دارد:content-prefs.sqlite, cookies.sqlite, downloads.sqlite, formhistory.sqlite, places.sqlite, permissions.sqlite, search.sqlite, signons.sqlite, urlclassifier3.sqlite and webappsstore.sqlite

SQLite مانند هر پايگاه‌داده‌ي ديگري بعد از مدتي داراي فضاي خالي بين داده ها و گسيختگي شده و نياز به دفرگ و مرتب سازي پيدا ميكند از آنجاييكه هيچ برنامه اي براي چك كردن و بهينه سازي پايگاه داده به طور پبش فرض در نظر گرفته نشده است افزايش حجم پايگاه داده سبب كاهش كارايي ، افزايش زمان جستجو و لود شدن برنامه و… ميشود.

يك كليك تا بهينه سازي فايرفاكس با SpeedyFox

SpeedyFox برنامه كوچك و جديد براي بهينه سازي و رفع مشكلات فايرفاكس فقط با يك كليك است بعد از اجراي نرم افزار سرعت فايرفاكس به طور قابل توجهي بيشتر شده و استفاده از فايرفاكس لذت بخش تر خواهد شد اين نرم‌افزار پوشه پروفايل را تشخيص داده و در ليستي نمايش ميدهد و تنها كاري كه نياز است انجام دهيد فشردن دكمه Speed Up My Firefox! است.

فرآيند بهينه سازي ميتواند به نسبت حجم تاريخچه فايرفاكس چند دقيقه طول بكشد. SpeedyFox فعلا فقط براي ويندوز منتشر شده است صفحه دانلود

يكپارچه سازي بانكهاي اطلاعاتي فايرفاكس با نرم افزار SQLite Manager:

1-SQLite Manager را از اينجا دانلود كنيد (لينك مستقيم دانلود جديدترين نسخه ويندوز)

2-فايل دانلود شده را از حالت فشرده خارج كرده و در پوشه پروفايل فايرفاكس كه فايلهاي .sqlite قرار دارند كپي كنيد (مسير پوشه پروفايل يا از سرچ *.sqlite استفاده كنيد) كپي كنيد

3- مطمئن باشيد فايرفاكس در حال اجرا نباشد و از خط فرمان دستور sqlite3.exe SQLiteDatabase VACUUM كه SQLiteDatabase را با نام ديتابيس جايگزين كنيد به عنوان مثال sqlite3.exe places.sqlite VACUUM

فايل موقتي با اسم places.sqlite-journal ايجاد شده و ديتابيس مرتب در آن  ساخته ميشود.

در ويندوز براي دفرگ كردن همه ديتابيسها ميتوان از دستور زير استفاده كرد:

for %a in (*.sqlite) do (sqlite3 %a vacuum) 

نتيجه چند تست:

ميتوان دستور دفرگ شدن ديتابيس هاي فايرفاكس را در ليست برنامه هايي كه به طور خودكار با ويندوز اجرا ميشوند گذاشت تا با هر بار شروع ويندوز فايرفاكس بهينه شود

روش ساده تر براي كاربران ويندوز استفاده از IniFox v 1.2 است كه با يك اسكريپت محل پروفايل را يافته و تمام ديتابيس‌هاي فايرفاكس رو دفرگ ميكند در اين روش نيازي به دستورات خط فرمان نيست و خيلي ساده تر است. دانلود IniFox +

در تصوير زير ميتوانيد حجم فايلهاي ديتابيس فايرفاكس را قبل و بعد  از اجراي SpeedyFox  مقايسه كنيد سرعت اين نسخه از فايرفاكس كه استفاده ميكنم به طرز قابل توجهي افزايش يافت.

منايع:

Easily Optimize Firefox SQLite Databases with SpeedyFox Portable

http://mozillalinks.org/wp/2009/07/vacuum-your-firefox-databases-for-better-performance