You get a palladium star for avoiding the most obvious source of errors (and 
wasted keystrokes) ... 

---
Theory is when you know everything but nothing works.  Practice is when 
everything works but no one knows why.  Sometimes theory and practice are 
combined:  nothing works and no one knows why.

>-----Original Message-----
>From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-
>boun...@sqlite.org] On Behalf Of Drago, William @ CSG - NARDAEAST
>Sent: Monday, 8 December, 2014 11:38
>To: General Discussion of SQLite Database
>Subject: Re: [sqlite] Table names length and content
>
>> -----Original Message-----
>> From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-
>> boun...@sqlite.org] On Behalf Of Richard Hipp
>> Sent: Monday, December 08, 2014 1:28 PM
>> To: General Discussion of SQLite Database
>> Subject: Re: [sqlite] Table names length and content
>>
>> On Mon, Dec 8, 2014 at 1:22 PM, jose isaias cabrera
>> <jic...@cinops.xerox.com
>> > wrote:
>>
>> >
>> > "Stephan Beal" wrote...
>> >
>> >  On Mon, Dec 8, 2014 at 6:32 PM, jose isaias cabrera <
>> >> jic...@cinops.xerox.com
>> >>
>> >>> wrote:
>> >>>
>> >>
>> >>  When creating table names, are there any constraints that one must
>> >> look
>> >>> for? ie. Length? Characters? etc.?  I quickly browse through this
>> >>> spot,
>> >>>
>> >>> https://www.sqlite.org/lang_createtable.html
>> >>>
>> >>
>> >>
>> >> https://www.sqlite.org/limits.html
>> >>
>> >> might have what you're looking for.
>> >>
>> >
>> > Hmmm... what I am looking for it is not there.  If the "string
>> length"
>> > defined there is what defines the length of the name of a table, I am
>> > in business. :-)  However, there is nothing about problematic
>> characters. ie.
>> > <>!@#$%^&*()_+=-{}\|[]'";:?/.,, etc., etc. in the table name.
>> >
>> >
>> Put the table name in double-quotes.
>
>Uh oh! I never use quotes when I create my tables. What are the
>implications of not quoting?
>
>-Bill
>CONFIDENTIALITY, EXPORT CONTROL AND DISCLAIMER NOTE:This e-mail and any
>attachments are solely for the use of the addressee and may contain
>information that is privileged or confidential. Any disclosure, use or
>distribution of the information contained herein is prohibited. In the
>event this e-mail contains technical data within the definition of the
>International Traffic in Arms Regulations or Export Administration
>Regulations, it is subject to the export control laws of the
>U.S.Government. The recipient should check this e-mail and any
>attachments for the presence of viruses as L-3 does not accept any
>liability associated with the transmission of this e-mail. If you have
>received this communication in error, please notify the sender by reply
>e-mail and immediately delete this message and any attachments.
>_______________________________________________
>sqlite-users mailing list
>sqlite-users@sqlite.org
>http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users



_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to