[sqlite] re: java jbdc test SOLVED

[j-marvin]

hi-
 
i am going to write down everything i did today (if i can remember).
i ran the test file and everything is ok.
 
thanks,
jim

[sqlite] re: java jdbc test problems

[j-marvin]

hi-
 
i am a little further along (i hope).
 
C:\sqlite-2.8.15>make test
MAKE Version 5.2  Copyright (c) 1987, 1998 Inprise Corp.
"C:\Program Files\Java\jdk1.5.0_01"\bin\javac test.java
 
C:\sqlite-2.8.15>
 
and when i go to look at the file test there is a test.class file now
as well as the test.java class.
 
i will keep trying things out.
 
thanks,
jim

[sqlite] java sqlite problems with test

[j-marvin]

hi-
 
i am attempting to learn java.  i tried to install the sqlite jdbc and
ran into these messages.
can someone who knows java better (especially all the make and
configuration stuff) offer some advice
as to what might be going wrong? 
 
C:\sqlite-2.8.15>make test
MAKE Version 5.2  Copyright (c) 1987, 1998 Inprise Corp.
"C:\Program Files\Java\jdk1.5.0_01"\bin\javac test.java
test.java:62: cannot find symbol
symbol  : variable Constants
location: class test
return Constants.SQLITE_OK;
   ^
test.java:84: cannot find symbol
symbol  : variable Constants
location: class test
db.function_type("myregfunc", Constants.SQLITE_TEXT);
  ^
test.java:86: cannot find symbol
symbol  : variable Constants
location: class test
db.function_type("myaggfunc", Constants.SQLITE_TEXT);
  ^
3 errors
 
** error 1 ** deleting test
 
C:\sqlite-2.8.15>java test
Exception in thread "main" java.lang.NoClassDefFoundError: test
 
C:\sqlite-2.8.15>

[sqlite] re: sqlite delphi strings

[j-marvin]

i thought about it some more.
i can code around it with some more delphi string functions.
the one string function i was using isnt quite enough.
 
i just needed to step away from the computer for awhile.
 
thanks,
jim

[sqlite] delphi sqlite strings

[j-marvin]

hi-
 
in my attempt to generate a createTable syntax when i come across the
default keyword i run into a slight problem.
 
i want to write DEFAULT'something could be more than one word'
it seems to get inserted as default \'something could be more than one
word\' into the sqlite table
 
one way around this i thought was to use the delphi function
stringreplace to take out the \ character.
while this works it leaves the possiblity that someone will actually
want the \ character inside the default 'some\thing could be more than
one word'
and the flag rfreplaceall wipes all of them out.
 
is there an easy way around this or should i just make a note in the
user instructions to go in and edit the auto generated
createTable statement file if they use \ character after the GUI build
createTable syntax routine runs?
 
i have looked at FAQ 16 and tried  or '' variations and nothing
seems to work.
 
thanks,
jim
 
 
 
 
 

RE: [sqlite] sqlite project--working with table structure

[j-marvin]

-Original Message-
From: Darren Duncan [mailto:[EMAIL PROTECTED] 
Sent: Saturday, November 20, 2004 3:14 PM
To: [EMAIL PROTECTED]
Subject: RE: [sqlite] sqlite project--working with table structure

-- Darren Duncan

ok Darren.  Thank you and the other posters for helping.
I will think about everything I read today before trying to proceed
any further with this very small project.  I didn't write a line of
code yet so hopefully I will get the design right before I start doing
that.

good luck with your ongoing SQL::Routine project.

thanks again,
jim

RE: [sqlite] sqlite project--working with table structure

[j-marvin]

Have a look here: http://search.cpan.org/dist/SQL-Routine/

That's part of a project I'm working on.  With it, each database 
table, as well as every other kind of thing you could possibly put in 
a schema or use with a database, is represented as a cross-referenced 
hierarchy of atomic-value nodes.

You can create and manipulate your "create table statement" by 
adding, removing, and altering the nodes.  Then the create can be 
generated from them when done.

-- Darren Duncan

jim wrote:
Darren, this is cool.  I can't wait to pass this along to a person
at my job who works with DB's at his full-time job.

I had thought wouldn't it be nice if people would agree on the table
structue of the create
table statement within the sqlite community for all these sqlite db
tools
popping up.  In my own self serving way in part at least because I am
not smart thought of 
the standardization because you just know I will mess up the table
relations design.
And like most projects who the hell wants the headache of maintaining
all the changes.
Why cant I borrow someone elses who did it before me who is smarter ;-)
I know it sounds incredibly lazy but because of my brain it takes me
longer to do things
so I often think of things to cut corners to help save time.
  I never dreamed a whole language spanning multiple db systems
would end up being developed.  And if you look at some tools out there I
believe the fancy 
structure change was omitted because of the headache to support my
theory.  Probably
a feature creep decision.

this looks like its required install OS is linux though???

thanks,
jim

[sqlite] sqlite project--working with table structure

[j-marvin]

hi-
 
i was hoping to get a little feedback on an idea i had.  
 
the create table statement can get complex with its variable number
field constraints and table constraints etc. etc.
when i first tackled the problem i tried to parse it.  now i have a
different idea.  what if i viewed the create table statement
as a group of tables with records .  then when i am finished adding
records to the structure db tables i could call 
a routine to write the create table statement based on the structure db
database for that particular table.
 
a problem i see with this design is someone with a table already
designed would not want to use a program like this
because they have all ready generated the table structure in
sqlite_master.sql.  
 
i'll probably be the only user anyways.
 
i thought i could use delphi personal edition and libsql to create an
interface in this manner to insert,update,delete,select
table structure data.
 
is this a really bad idea?  i have to try something.  changing the
structure is the worst part of my program :-(
 
thanks,
jim

[sqlite] column def vs. constraint at end of create table stmt

[j-marvin]

hi-

I am working on making my program for viewing sql statement results and
changing table structure a little nicer.  the reason the question came
about below is I thought I'd like to add capability to have more than
one field be the primary key and also would like to add the constraint
unique to work the same.

if I have a column def statement for every field and specify unique and
primary constraints in each column def, what is the reason the
constraint that goes on the very end of the create table would be needed
[, constraint]*  

 column-def ::= name [type] [[CONSTRAINT name] column-constraint]* 

 sql-command ::= CREATE [TEMP | TEMPORARY] TABLE table-name (
column-def [, column-def]*
[, constraint]*
) 

thank you very much,
jim