What database software can we use in Puppy?
-
- Posts: 8
- Joined: Sun 26 Oct 2008, 02:44
What database software can we use in Puppy?
Me and my friend want to make accounting software in puppy linux base, but we doesn't know what database we can use and how to combine it with C++.
thank's for your help.
thank's for your help.
Hi,
I noticed the other day that puppy has sqlite installed in it.
If you go to a terminal and type:
sqlite3 mydatabase.db
it creates a new database and you can type any normal sql statements in and it will happly create tables, insert values, update values, run selects.
I believe that sqlite has loads of bindings for all kinds of languages.
I hope this helps.
I noticed the other day that puppy has sqlite installed in it.
If you go to a terminal and type:
sqlite3 mydatabase.db
it creates a new database and you can type any normal sql statements in and it will happly create tables, insert values, update values, run selects.
I believe that sqlite has loads of bindings for all kinds of languages.
I hope this helps.
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
Database discussion
http://www.murga-linux.com/puppy/viewto ... 295#118295
LAMP (Puppy Style)
http://www.murga-linux.com/puppy/viewto ... 547#224547
http://www.murga-linux.com/puppy/viewto ... 295#118295
LAMP (Puppy Style)
http://www.murga-linux.com/puppy/viewto ... 547#224547
sqlite is actually quite powerful. It has c/c++ bindings. It can also work with php or tcl/tk, although I don't know if the version in Puppy is the complete version. It's definitely not the most up to date version, but it's current enough to be very useful.
http://www.sqlite.org/
http://www.sqlite.org/
The newest release of the sqlite frontend, tkqlite-0.5.7, was released on 17/11/2008. The linked binary is standalone, and doesn't require any additional tcl/tk libraries.
-
- Posts: 1
- Joined: Wed 10 Dec 2008, 15:25
What database software we can use.
he organization shown above suggests that each character instance image is storage in a separate file. In fact, the physical organization of the database is quite different. Typical database queries at CEDAR, such as a classifier training job, rapidly access a large number of characters. Were each character stored in a separate file, the retrieval overhead would be impractically high. Instead, all images for a particular JIS code are stored in a single file. Software simulates the logical organization shown above.http://www.virtualizationteam.com/virtu ... sx-40.html
A new release of sqlitestudio is available.
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
Just run the bin file, first right click it, then select permissions, and select a+x (Make executable/searchable) click, Quiet then ok and thats it, it will run. any problems with that, I'll make a package or maybe muggins for you.muggins wrote:A new release of sqlitestudio is available.
http://sqlitestudio.one.pl/files/free/s ... -1.1.0.bin
ttuuxxx
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
Let me start off by saying I'm not any kind of database guru, but I have worked at least some with Access, Open Office Base, Sequel, and a few others, so I have a smattering of fairly shallow experience.
After only the most basic testing -- Sqlitestudio is great.
1. It helps me build tables very quickly.
2. Entering data is easy, although I wish the tab key would move me to the next field instead of entering an actual tab.
3. The only problem I have run into so far, is that the sql results won't export. I get a big list of errors that I haven't dissected yet. I'd like to get my results to a comma delimited list to merge with my documents, but so far no dice.
I'll keep working as time permits.
After only the most basic testing -- Sqlitestudio is great.
1. It helps me build tables very quickly.
2. Entering data is easy, although I wish the tab key would move me to the next field instead of entering an actual tab.
3. The only problem I have run into so far, is that the sql results won't export. I get a big list of errors that I haven't dissected yet. I'd like to get my results to a comma delimited list to merge with my documents, but so far no dice.
I'll keep working as time permits.
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
maybe next time post the errors here? And we'll see if we can help you out somehillside wrote:Let me start off by saying I'm not any kind of database guru, but I have worked at least some with Access, Open Office Base, Sequel, and a few others, so I have a smattering of fairly shallow experience.
After only the most basic testing -- Sqlitestudio is great.
1. It helps me build tables very quickly.
2. Entering data is easy, although I wish the tab key would move me to the next field instead of entering an actual tab.
3. The only problem I have run into so far, is that the sql results won't export. I get a big list of errors that I haven't dissected yet. I'd like to get my results to a comma delimited list to merge with my documents, but so far no dice.
I'll keep working as time permits.
ttuuxxx
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
Well, I guess if you insist.maybe next time post the errors here? And we'll see if we can help you out some
I was going to spend some more time on this myself before posting anything detailed here, but more eyes, and brains, are usually better.
I was able to build a table, enter data, and run a simple SQL query successfully. Everything seems to work about as expected. The query returns exactly the data that I had expected it to. But, when I try to export the results of my query, I get errors. Usually the file that the exported info is to go into is created, but it's empty.
The table and SQL are extremely basic. I was only doing this as an initial test. I don't think I have any problems with how they are created. Plus, they seem to work very well until I try to export.
The export error info is as follows:
Code: Select all
invalid command name ""
while executing
"$db eval $query R {
set cols $R(*)
set row [list]
foreach c $R(*) {
lappend row $R($c)
}
lappend data $row
}"
("results" arm line 8)
invoked from within
"switch -- $type {
"database" {
switch -- [$res get format] {
"SQL" {
set ret [exportDatabaseAsSQL $db $dbonly [$res get sql:null]]
..."
while executing
"error $::errorInfo"
invoked from within
"if {$catchCode} {
error $::errorInfo
}"
("uplevel" body line 98)
invoked from within
"uplevel 2 "
set catchCode 0
if {\[catch {
$body1
} error]} {
set catchCode [catch {$body2}]
}
$body2
if {\$catchCode} {
error \$:..."
(procedure "_tryfinally" line 2)
invoked from within
"_tryfinally [lindex $args 0] [lindex $args 2]"
(procedure "try" line 7)
invoked from within
"try {
switch -- $type {
"database" {
switch -- [$res get format] {
"SQL" {
set ret [exportDatabaseAsSQL $db $dbonly [$res get sql:..."
(procedure "::MainExport::parseExportDialogResults" body line 16)
invoked from within
"MainExport::parseExportDialogResults $ret results"
("results" arm line 2)
invoked from within
"switch -- $_type {
"database" {
set res [MainExport::parseExportDialogResults $ret database]
}
"table" {
set res [MainExport::parseExportD..."
(object "::.resultsExportDialog" method "::ExportDialog::okClicked" body line 76)
invoked from within
"okClicked"
("default" arm line 3)
invoked from within
"switch -- $bt {
"cancel" {
set retval [cancelClicked]
}
default {
set okBtn 1
set retval [okClicked]
}
}"
(object "::.resultsExportDialog" method "::Modal::clicked" body line 3)
invoked from within
"::.resultsExportDialog clicked ok"
invoked from within
".resultsExportDialog.f.btn.export invoke "
invoked from within
".resultsExportDialog.f.btn.export instate {pressed !disabled} { .resultsExportDialog.f.btn.export state !pressed; .resultsExportDialog.f.btn.export in..."
(command bound to event)
@Hillside,
unfortunately I know little about sql, so can't help you there. But I wonder whether you've tried exporting your table with either sqlite-manager, which can be used as a firefox/seamonkey plugin, or with tksqlite
unfortunately I know little about sql, so can't help you there. But I wonder whether you've tried exporting your table with either sqlite-manager, which can be used as a firefox/seamonkey plugin, or with tksqlite
Thanks for the tips, Muggins.
Both of those options look like they will require some serious
upgrading to my old and feeble system, so I may pass on them for
now.
I've been using OObase and don't really need a new database
system, but I feel that database management for the desktop is a
weak area in Linux and was excited to see a new potential solution.
I actually can make it work by doing some cutting and pasting
instead of using the export function, but full functionality is what I'm
hoping for. I can also just use sqlite from the command line, but I
think a more graphical tool is what is really needed.
I think sqlitestudio has a lot of potential and am looking forward to
the next version that comes out. It's close to being a tool for the
masses.
Both of those options look like they will require some serious
upgrading to my old and feeble system, so I may pass on them for
now.
I've been using OObase and don't really need a new database
system, but I feel that database management for the desktop is a
weak area in Linux and was excited to see a new potential solution.
I actually can make it work by doing some cutting and pasting
instead of using the export function, but full functionality is what I'm
hoping for. I can also just use sqlite from the command line, but I
think a more graphical tool is what is really needed.
I think sqlitestudio has a lot of potential and am looking forward to
the next version that comes out. It's close to being a tool for the
masses.
AFAIK neither should require any upgrade. Tksqlite, while being tcl/tk based, comes in a completely self-contained, ready to run, executable. If it doesn't have the functionality you require, just delete the one file.
Whereas sqlitemanager you can just download the .xpi file, open it with firefox, or seamonkey, and install it as a plugin. Maybe one problem with doing this with seamonkey is that if you don't like the app, it's not as easy to uninstall as with firefox.
Whereas sqlitemanager you can just download the .xpi file, open it with firefox, or seamonkey, and install it as a plugin. Maybe one problem with doing this with seamonkey is that if you don't like the app, it's not as easy to uninstall as with firefox.
@hillside
next version (1.1.1) of sqlitestudio is out.
http://sqlitestudio.one.pl/index.rvt?act=download
cheers
aragon
next version (1.1.1) of sqlitestudio is out.
http://sqlitestudio.one.pl/index.rvt?act=download
cheers
aragon
PUPPY SEARCH: http://wellminded.com/puppy/pupsearch.html
Hi, I'm SQLiteStudio developer.
Please report bugs to to sqlitestudio bug track system ( http://sqlitestudio.one.pl/index.rvt?act=bug ). You don't have to report this bug above, since I've read it here
I didn't met this error before, so I didn't fix it in 1.1.1. I'll fix it in version 1.1.2.
Please tell me a detail:
Did you execute SQL query, then disconnect from database file, then tried to export data? I need to know if you closed database before exporting. It might be reason (which I should fix).
Please report bugs to to sqlitestudio bug track system ( http://sqlitestudio.one.pl/index.rvt?act=bug ). You don't have to report this bug above, since I've read it here
I didn't met this error before, so I didn't fix it in 1.1.1. I'll fix it in version 1.1.2.
Please tell me a detail:
Did you execute SQL query, then disconnect from database file, then tried to export data? I need to know if you closed database before exporting. It might be reason (which I should fix).