> What's the objection to reading your SQL source out of the database and
> preparing it at program startup?
I have no objection to reading the sql on startup as that is what we are
currently doing. I just want all data access code inside of the database
instead of my source code. Does anyone
when i use this code:
(Omit some code...such as sqite3_stmt)
sqlite3_prepare("select * from table1 where $fieldname = $fieldvalue")
sqlite3_bind_text("$fieldname", "id"); //the "id" is a field of table1,
this line maybe got error.
sqlite3_bind_int("$fieldvalue", 5);
sqlite3_step();
...
I wonder
On Mon, 9 May 2005, Helmut Tschemernjak wrote:
Hello,
sqlite3 3.2.1 gives SQLITE_LOCKED errors if one process updates the database
and another accesses it. Most retries will fail if the other processes is
working e.g. many inserts.
Here is my idea:
Keep a list of up to 32 pid_t of waiting
Hello,
I like to recommend to use an enum for the return code of all sqlite3
functions., E.g.:
typedef enum {
SQLITE_OK = 0,/* Successful result */
SQLITE_ERROR= 1,/* SQL error or missing database */
SQLITE_INTERNAL = 2,/* An internal logic error in
Sombra schrieb:
There is any Datatypes for Data (year, moth,day ) in version 2.8.16 of
SQLite?
Thanks
SB
No, there isn't.
you can save a time_t or even a COleDateTime::m_dt in the database.
Yours
Martin
On Mon, May 09, 2005 at 08:20:14AM -0700, David M. Cook wrote:
> CREATE VIEW flat_recording_view as select r.recording_id, c.composer_name,
> SQL error: no such column: composer_name
>
> Aliasing the column names in the view using the 'as' syntax didn't help.
I guess I mistyped my query,
There is any Datatypes for Data (year, moth,day ) in version 2.8.16 of
SQLite?
Thanks
SB
I have a view
CREATE VIEW flat_recording_view as select r.recording_id, c.composer_name,
w.title, r.description, l.label_name, d.catalog_no from composer c join work
w on (c.composer_id=w.composer_id) join recording r on (w.work_id=r.work_id)
join disc d on (r.disc_id=d.disc_id) join label l on
While playing around with the extension of the order_number question Dave posted
I got stuck at some point.
I have 3 triggers on a table for INSER/DELETE and UPDATE.
all 3 of them do further UPDATEs on the same table.
How can I make sure that these UPDATEs won't fire the UPDATE trigger again ?
For original announcement with links see
http://www.kexi-project.org/wiki/wikiview/index.php?0.9Beta1Announcement
== Kexi 0.9 beta 1 Announcement ==
Kexi Team Ships Beta Release of Major Enhancements to Free Integrated Database
Environment
May 9, 2005 (The INTERNET). The Kexi Team today announced
On 5/9/05, Brown, Dave <[EMAIL PROTECTED]> wrote:
>
> The question I have is: If a row gets deleted, how do I sequentially reorder
> the remaining
> rows? For example:
>
> Start with this:
> a, 1
> b, 2
> c, 3
> d, 4
>
> now delete the row with 'b':
>
> a, 1
> c, 3
> d, 4
>
> I'm trying to
11 matches
Mail list logo