Best free database to use with PB to create shareware?
-
Noble Bell
- User

- Posts: 34
- Joined: Sun Jun 04, 2006 8:49 pm
- Location: Kentucky, USA
- Contact:
Best free database to use with PB to create shareware?
Hello again,
So, what would you say is the best and FREE database to use with PB? I have at my disposal: Tsunami and Cheetah. Is there something easier and better to use for shareware development?
Thanks in advance,
So, what would you say is the best and FREE database to use with PB? I have at my disposal: Tsunami and Cheetah. Is there something easier and better to use for shareware development?
Thanks in advance,
- Thorsten1867
- Addict

- Posts: 1372
- Joined: Wed Aug 24, 2005 4:02 pm
- Location: Germany
I use SQLite3 (PBOSL) in my programs.
Translated with http://www.DeepL.com/Translator
Download of PureBasic - Modules
Download of PureBasic - Programs
[Windows 11 x64] [PB V5.7x]
Download of PureBasic - Modules
Download of PureBasic - Programs
[Windows 11 x64] [PB V5.7x]
It depends of what you need. Local or Distant database ?
you seems to speak about local ones, so there's also SQLite3 which is quite very good. Never tested Cheetah nor Tsunami but there are includes on the forum for them.
[EDIT]
3 votes for SQLite in 2 small minutes.
SQLite win !
you seems to speak about local ones, so there's also SQLite3 which is quite very good. Never tested Cheetah nor Tsunami but there are includes on the forum for them.
[EDIT]
3 votes for SQLite in 2 small minutes.
No programming language is perfect. There is not even a single best language.
There are only languages well suited or perhaps poorly suited for particular purposes. Herbert Mayer
There are only languages well suited or perhaps poorly suited for particular purposes. Herbert Mayer
-
Noble Bell
- User

- Posts: 34
- Joined: Sun Jun 04, 2006 8:49 pm
- Location: Kentucky, USA
- Contact:
I'm a relative newbie to sqlite and selected it because of the overall level of support both here (primarily) and external.
Can't really speak for the others although I have heard some nice things about them all, sqlite seems to be the most popular (and supported) by the PB community.
That said, if you wander into 'blob" territory, the support level might drop a bit
cheers
Can't really speak for the others although I have heard some nice things about them all, sqlite seems to be the most popular (and supported) by the PB community.
That said, if you wander into 'blob" territory, the support level might drop a bit
cheers
-
Noble Bell
- User

- Posts: 34
- Joined: Sun Jun 04, 2006 8:49 pm
- Location: Kentucky, USA
- Contact:
- netmaestro
- PureBasic Bullfrog

- Posts: 8452
- Joined: Wed Jul 06, 2005 5:42 am
- Location: Fort Nelson, BC, Canada
Recycling a topic rather than creating a new one (but changing tack a little).
How do you guys handle table maintenance in sqlite, specifically dropping a column from a table (which the docs appear to say sqlite does not support)?
Do you export everything except the unwanted column/field, then delete the table, create a new one and import? Or is there some simpler way?
Also, do you know if anyone has created a static lib for sqlite?
Thanks!
How do you guys handle table maintenance in sqlite, specifically dropping a column from a table (which the docs appear to say sqlite does not support)?
Do you export everything except the unwanted column/field, then delete the table, create a new one and import? Or is there some simpler way?
Also, do you know if anyone has created a static lib for sqlite?
Thanks!
Dare2 cut down to size
I took a tip from Thorsten1867 (I think?
) in which he suggested that instead of battling SQLite's inability to natively drop a column, create a second table used to hold those columns for the first table which may be deleted at some point.
E.g.
MainTable <ID> <fixed col 1> <fixed col 2> ... etc.
SecondTable <ID> <column name> <column data>
The tables are linked by the ID fields.
This way, deleting a column simply involves deleting all records in the second table for which the <column name> field matches a given column name etc.
It works very well for me and avoids the hassle of creating temporary tables etc.
E.g.
MainTable <ID> <fixed col 1> <fixed col 2> ... etc.
SecondTable <ID> <column name> <column data>
The tables are linked by the ID fields.
This way, deleting a column simply involves deleting all records in the second table for which the <column name> field matches a given column name etc.
It works very well for me and avoids the hassle of creating temporary tables etc.
I may look like a mule, but I'm not a complete ass.
-
dracflamloc
- Addict

- Posts: 1648
- Joined: Mon Sep 20, 2004 3:52 pm
- Contact:

