On Jan 16, 1:47 am, gert wrote:
> except sqlite3.Error as e:
> ERROR = "Error " + ...
>
> how does except work in python3 ?
except sqlite3.Error as e:
ERROR = "Error " + e.args[0]
oops i thought it did not work somehow in 3.0 but it does :)
--
http://
except sqlite3.Error as e:
ERROR = "Error " + ...
how does except work in python3 ?
--
http://mail.python.org/mailman/listinfo/python-list
"Florian Diesch" <[EMAIL PROTECTED]>wrote:
8<--
>In Germany "von" is just a part of the name since 1919 when the nobility
>was abolished by law.
Thanks - was not aware of this - 1919 - just after the Great War, 1914-1918...
- Hendrik
"Hendrik van Rooyen" <[EMAIL PROTECTED]> wrote:
> "Lawrence D'Oliveiro" <[EMAIL PROTECTED]> wrote:
>
>
>> In message <[EMAIL PROTECTED]>, Hendrik van
>> Rooyen wrote:
>>
>> > "Lawrence D'Oliveiro" <[EMAIL PROTECTED]> wrote:
>> >
>> > 8<
>> >
John J. Lee wrote:
> Steve Holden <[EMAIL PROTECTED]> writes:
> [...]
> > > There would also need to be a flag field to indicate the canonical
> > > ordering
> > > for writing out the full name: e.g. family-name-first, given-names-first.
> > > Do we need something else for the Vietnamese case?
> >
Theerasak Photha wrote:
> On 10/7/06, Lawrence D'Oliveiro <[EMAIL PROTECTED]> wrote:
>
>
>>Just because most Western designers of databases do it wrong doesn't mean
>>that a) you should do it wrong, or b) they will continue to do it wrong
>>into the future, as increasing numbers of those designer
On 10/7/06, Lawrence D'Oliveiro <[EMAIL PROTECTED]> wrote:
> Just because most Western designers of databases do it wrong doesn't mean
> that a) you should do it wrong, or b) they will continue to do it wrong
> into the future, as increasing numbers of those designers come from Asian
> and other n
Hendrik van Rooyen schreef:
> "Lawrence D'Oliveiro" <[EMAIL PROTECTED]> wrote:
>
>
>> In message <[EMAIL PROTECTED]>, Hendrik van
>> Rooyen wrote:
>>
>>> "Lawrence D'Oliveiro" <[EMAIL PROTECTED]> wrote:
>>>
>>> 8<
>>>
I wonder if we nee
"Lawrence D'Oliveiro" <[EMAIL PROTECTED]> wrote:
> In message <[EMAIL PROTECTED]>, Hendrik van
> Rooyen wrote:
>
> > "Lawrence D'Oliveiro" <[EMAIL PROTECTED]> wrote:
> >
> > 8<
> >
> >> I wonder if we need another "middle" field for holding
John J. Lee wrote:
> "John Machin" <[EMAIL PROTECTED]> writes:
> [...]
> > This is all a bit OT. Before we close the thread down
>
> Do you have a warrant for that?
I have some signed-but-otherwise-blank warrants, but I'm saving them
for other threads :-)
>
> > , let me leave
> > you with one w
"John Machin" <[EMAIL PROTECTED]> writes:
[...]
> This is all a bit OT. Before we close the thread down
Do you have a warrant for that?
> , let me leave
> you with one warning:
> Beware of enthusiastic maintenance programmers on a mission to clean up
> the dirty names in your database:
> E.g. (1
Steve Holden <[EMAIL PROTECTED]> writes:
[...]
> > There would also need to be a flag field to indicate the canonical
> > ordering
> > for writing out the full name: e.g. family-name-first, given-names-first.
> > Do we need something else for the Vietnamese case?
>
> You'd think some standards bod
"Dennis Lee Bieber" <[EMAIL PROTECTED]>wrote:
8<--
> In the days of paper filing (I actually took Shorthand, and a
> Business Machines & Filing course in High School to avoid Phys.Ed.) the
> training for things like oriental names was to choose one for "surname
Steve Holden wrote:
>
> Don't forget the UK, where the scots are accommodated by filing Mc
> before Mac everywhere except the 'phone book, where IIRC they are
> treated as equivalent.
Same/similar phone book treatment here in Australia -- Mc is treated as
though it were spelled Mac. An interestin
In message <[EMAIL PROTECTED]>, Hendrik van
Rooyen wrote:
> "Lawrence D'Oliveiro" <[EMAIL PROTECTED]> wrote:
>
> 8<
>
>> I wonder if we need another "middle" field for holding the "bin/binte"
>> part (could also hold, e.g. "Van" for those n
Lawrence D'Oliveiro wrote:
> In message <[EMAIL PROTECTED]>, John
> Machin wrote:
>
>
>>Two problems so far:
>>(1) If you then assume that you should print the phone directory in
>>order of family name, that's not appropriate in some places e.g.
>>Iceland; neither is addressing Jon Jonsson as "Mr
"Lawrence D'Oliveiro" <[EMAIL PROTECTED]> wrote:
8<
> I wonder if we need another "middle" field for holding the "bin/binte" part
> (could also hold, e.g. "Van" for those names that use this).
NO! - I think of my surname as "van Rooyen"
In message <[EMAIL PROTECTED]>, John
Machin wrote:
> Two problems so far:
> (1) If you then assume that you should print the phone directory in
> order of family name, that's not appropriate in some places e.g.
> Iceland; neither is addressing Jon Jonsson as "Mr Jonsson", and BTW it
> can be their
Steve Holden <[EMAIL PROTECTED]> writes:
> > There would also need to be a flag field to indicate the canonical
> > ordering
> > for writing out the full name: e.g. family-name-first, given-names-first.
> > Do we need something else for the Vietnamese case?
>
> You'd think some standards body woul
Lawrence D'Oliveiro wrote:
> In message <[EMAIL PROTECTED]>, Steve
> Holden wrote:
>
>
>>John Machin wrote:
>>
>>[lots of explanation about peculiarities of people's names]
>>
>>While I don't dispute any of this erudite display of esoteric
>>nomenclature wisdom the fact remains that many (predomi
Lawrence D'Oliveiro wrote:
> In message <[EMAIL PROTECTED]>, Steve
> Holden wrote:
>
> > John Machin wrote:
> >
> > [lots of explanation about peculiarities of people's names]
> >
> > While I don't dispute any of this erudite display of esoteric
> > nomenclature wisdom the fact remains that many (p
In message <[EMAIL PROTECTED]>, Steve
Holden wrote:
> John Machin wrote:
>
> [lots of explanation about peculiarities of people's names]
>
> While I don't dispute any of this erudite display of esoteric
> nomenclature wisdom the fact remains that many (predominantly Western)
> databases do tend to
John Machin wrote:
> The problems are (1) there are cultures that don't have the concept of
> a surname, and if they do, it may not be the "last name" (2) the name
> may consist of only one word (giving you problems with "not null") or
> not even be a word.
>
> It gets better:
>
> Iceland: Jon B
Steve Holden wrote:
> John Machin wrote:
> > John Salerno wrote:
> >
> >>John Machin wrote:
> >>
> >>>John Salerno wrote:
> >>>
> CREATE TABLE Researchers (
> researcherID varchar(9) PRIMARY KEY NOT NULL,
> birthYear int(4) DEFAULT NULL,
> birthMonth int(2) DEFAULT N
John Machin wrote:
> John Salerno wrote:
>
>>John Machin wrote:
>>
>>>John Salerno wrote:
>>>
CREATE TABLE Researchers (
researcherID varchar(9) PRIMARY KEY NOT NULL,
birthYear int(4) DEFAULT NULL,
birthMonth int(2) DEFAULT NULL,
birthDay int(2) DEFAULT NULL
"John Machin" <[EMAIL PROTECTED]> writes:
> It gets better:
>
> Iceland:...
> Portuguese:...
> [parts of] Somalia, Ethiopia:...
> Vietnamese:...
You might add something about Arabic filionyms.
--
http://mail.python.org/mailman/listinfo/python-list
John Salerno wrote:
> John Machin wrote:
> > John Salerno wrote:
> >> CREATE TABLE Researchers (
> >> researcherID varchar(9) PRIMARY KEY NOT NULL,
> >> birthYear int(4) DEFAULT NULL,
> >> birthMonth int(2) DEFAULT NULL,
> >> birthDay int(2) DEFAULT NULL,
> >> birthCountry
Dennis Lee Bieber wrote:
> On Thu, 28 Sep 2006 14:05:16 GMT, John Salerno
> <[EMAIL PROTECTED]> declaimed the following in comp.lang.python:
>
>> I don't see this. The code works now, though. Maybe it was something
>> carried over by pasting.
>
> Here's a snippet from your original listing
Dennis Lee Bieber wrote:
> On Wed, 27 Sep 2006 18:41:54 GMT, John Salerno
> <[EMAIL PROTECTED]> declaimed the following in comp.lang.python:
>
>> You're right! I think that must have been leftover from when it wasn't
>> the last line in the query. Thanks!
>
> You also, based upon the cut&p
John Machin wrote:
> John Salerno wrote:
>> CREATE TABLE Researchers (
>> researcherID varchar(9) PRIMARY KEY NOT NULL,
>> birthYear int(4) DEFAULT NULL,
>> birthMonth int(2) DEFAULT NULL,
>> birthDay int(2) DEFAULT NULL,
>> birthCountry varchar(50) DEFAULT NULL,
>> bi
John Salerno wrote:
> CREATE TABLE Researchers (
> researcherID varchar(9) PRIMARY KEY NOT NULL,
> birthYear int(4) DEFAULT NULL,
> birthMonth int(2) DEFAULT NULL,
> birthDay int(2) DEFAULT NULL,
> birthCountry varchar(50) DEFAULT NULL,
> birthState char(2) DEFAULT NU
Tim Chase wrote:
> My guess would be the extra comma on the nameGiven line...most SQL
> engines I've used would choke on that
>
> - nameGiven varchar(255) DEFAULT NULL,
> + nameGiven varchar(255) DEFAULT NULL
You're right! I think that must have been leftover from when it wasn't
the
> import sqlite3
>
> con = sqlite3.connect('labdb')
> cur = con.cursor()
> cur.executescript('''
> DROP TABLE IF EXISTS Researchers;
> CREATE TABLE Researchers (
> researcherID varchar(9) PRIMARY KEY NOT NULL,
> birthYear int(4) DEFAULT NULL,
> birthMonth int(2) DEFAULT NULL,
>
Here's my script:
import sqlite3
con = sqlite3.connect('labdb')
cur = con.cursor()
cur.executescript('''
DROP TABLE IF EXISTS Researchers;
CREATE TABLE Researchers (
researcherID varchar(9) PRIMARY KEY NOT NULL,
birthYear int(4) DEFAULT NULL,
birthMonth int(2) DEFAULT NULL,
bi
34 matches
Mail list logo
