dbfpy-users

[Dbfpy-users] VFP9 and the _nullFlags field

[Jason M. <ja...@on...>]

Hello,
Apparently VFP 9 introduced an optional feature that adds a hidden field to
a DBF file called "_nullFlags".
More information:
http://www.matrixlist.com/pipermail/harbour/2007-October/004290.html
I was working with a DBF file that had this and caused dbfpy to fail. The
typeCode for _nullFlags is 0 (zero), so I tied adding a news class to
fields.py with the same properties as the class "DbfCharacterFieldDef", with
the exception of the typeCode. That seemed to fix it, at least for the file
I was working with. The class would need some work to take advantage of the
added features, but here's that class that should prevent the error I had by
at least being aware of the new field;
[begin code]
class DbfNullFlagsFieldDef(DbfFieldDef):
    """Definition of the _nullFlags field."""

    typeCode = "0"
    defaultValue = ""

    def decodeValue(self, value):
        """Return string object.

        Return value is a ``value`` argument with stripped right spaces.

        """
        return value.rstrip(" ")

    def encodeValue(self, value):
        """Return raw data string encoded from a ``value``."""
        return str(value)[:self.length].ljust(self.length)
[end code]

Thanks,
Jason (jmcpheron)

Re: [Dbfpy-users] UTF-8

[Yaroslav S. <ya...@gm...>]

Oh, thanks Alex. Now I got the problem. I should read things thoroughly.

On 07.07.2010, at 17:22, alexander smishlajev wrote:

> Dennis Follensbee wrote, at 07.07.2010 15:16:
>>
>> I’ve been a user of dbfpy for a number of years, now, and I’m  
>> curious if it supports utf-8.
>
> although there may be a code page indication in a dbf file, dbfpy  
> has no
> handling for it.  character strings are read and written as is,  
> without
> character translation, and there is no way to set the code page for  
> dbf
> file (other than using your own DbfHeader class with overridden  
> toString
> method).
>
> however, utf-8 is not a code page and is not supported by the code  
> page
> indicator.  the list of supported code pages is here:
> http://msdn.microsoft.com/en-US/library/8t45x02s%28v=VS.80%29.aspx
>
> best wishes,
> alex.
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Dbfpy-users mailing list
> Dbf...@li...
> https://lists.sourceforge.net/lists/listinfo/dbfpy-users
>

Re: [Dbfpy-users] UTF-8

[alexander s. <al...@go...>]

Dennis Follensbee wrote, at 07.07.2010 15:16:
>
> I’ve been a user of dbfpy for a number of years, now, and I’m curious if it supports utf-8.

although there may be a code page indication in a dbf file, dbfpy has no 
handling for it.  character strings are read and written as is, without 
character translation, and there is no way to set the code page for dbf 
file (other than using your own DbfHeader class with overridden toString 
method).

however, utf-8 is not a code page and is not supported by the code page 
indicator.  the list of supported code pages is here: 
http://msdn.microsoft.com/en-US/library/8t45x02s%28v=VS.80%29.aspx

best wishes,
alex.

Re: [Dbfpy-users] UTF-8

[Yaroslav S. <ya...@gm...>]

On 07.07.2010, at 14:16, Dennis Follensbee wrote:

> Hello-
>
> I’ve been a user of dbfpy for a number of years, now, and I’m  
> curious if it supports utf-8. I tried, for example, writing a  
> Unicode character to a dbf and got garbage in the output.

 >>> from dbfpy import dbf
 >>> db = dbf.Dbf('test.dbf')
 >>> for rec in db: print rec["name"].decode("utf-8")
...
€


What type of garbage do you have in the output?


> I’m developing this dbf for use in ArcGIS.
>
> Here is an example:
>
> # -*- coding: utf8 -*-
> from dbfpy import dbf
>
> def Test123(sOutDir):
>     pOutDBF = dbf.Dbf(sOutDir, new=True)
>     pOutDBF.addField(("NAME", "C", 105))
>     return pOutDBF
>
> def ProcessIt():
>     dbWriter = Test123(r"test.dbf")
>     fdWriter = open("test.txt", "w")
>     s = u"€"
>     pRec = dbWriter.newRecord()
>     fdWriter.write(s.encode("utf8"))
>     pRec["NAME"] = s.encode("utf-8")
>     pRec.store()
>     fdWriter.close()
>     dbWriter.close()
>
> ProcessIt()
>
>
> Dennis Follensbee | GIS Product Engineer | BroadMap LLC | Lebanon,  
> NH, United States | e-mail: den...@br... | office:  
> 603.678.4477 | www.broadmap.com | Twitter@BroadMap
> <image001.png>
> P Please consider the environment before printing this e-mail.
>
> This email and any files transmitted with it are confidential and  
> intended solely for the use of the individual/entity to which they  
> are addressed. If you have received this email in error please let  
> us know by e-mail reply and delete it from your system. You may not  
> copy this message or disclose its contents to anyone. E-mail  
> transmission cannot be guaranteed to be secure or error-free as  
> information could arrive late, be intercepted, corrupted, lost or  
> destroyed, be incomplete, or contain viruses. The sender therefore  
> does not accept liability for any viruses, errors or omissions in  
> the contents of this message, which arise as a result of e-mail  
> transmission. BroadMap LLC, 11543-A Nuckols Road, Glen Allen, VA  
> 23059. www.BroadMap.com
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first_______________________________________________
> Dbfpy-users mailing list
> Dbf...@li...
> https://lists.sourceforge.net/lists/listinfo/dbfpy-users

Re: [Dbfpy-users] add new field in a existing dbf

[alexander s. <al...@ty...>]

Alonso Luján Torres Taño wrote, at 11.08.2009 13:55:
> 
> I'm trying to modify a dbf adding a new field in a python script, but I 
> can't.
> 
> Just I can add a field in new dbf created in the same script.
> 
> I tryed with:
> 
>     db = dbf.Dbf("../filesource.dbf",new =False, readOnly=False)
>     ...
>     db.addField(("PESO","N",32,8))
> 
> and return error:
> 
>     Traceback (most recent call last):
>       File "script.py", line 34, in <module>
>         db.addField(("PESO","N",32,8))
>       File "/usr/lib/python2.5/site-packages/dbfpy/dbf.py", line 229, in addField
>         "structure can't be changed")
>     TypeError: ('At least one record was added, ', "structure can't be changed")

you should create new dbf with desired structure and copy data.

best wishes,
alex.

[Dbfpy-users] add new field in a existing dbf

[Alonso L. T. T. <lu...@ce...>]

Hi!

I'm trying to modify a dbf adding a new field in a python script, but I 
can't.

Just I can add a field in new dbf created in the same script.

I tryed with:

    db = dbf.Dbf("../filesource.dbf",new =False, readOnly=False)
    ...
    db.addField(("PESO","N",32,8))

and return error:

    Traceback (most recent call last):
      File "script.py", line 34, in <module>
        db.addField(("PESO","N",32,8))
      File "/usr/lib/python2.5/site-packages/dbfpy/dbf.py", line 229, in
    addField
        "structure can't be changed")
    TypeError: ('At least one record was added, ', "structure can't be
    changed")


I have not idea of what error I make.

If someone can help me, I'll so gratefull.

Thanks!

[Dbfpy-users] dbfpy included in the Softpedia Linux software database

[Softpedia E. T. <lin...@so...>]

Congratulations,

dbfpy, one of your products, has been added to Softpedia's database of
software programs for Linux. It is featured with a description text,
screenshots, download links and technical details on this page:
http://linux.softpedia.com/get/Programming/Libraries/dbfpy-47925.shtml

The description text was created by our editors, using sources such as
text from your product's homepage, information from its help system, the
PAD file (if available) and the editor's own opinions on the program
itself.



If you feel that having your product listed on Softpedia is not a benefit
for you or simply need something changed or updated, please contact us via
email at web...@so... and we will work with you to fix any
problem you may have found with the product's listing.

-- 
Sincerely,
The Softpedia Team

-----------------------------------------------------------------------
Softpedia is a library of over 400,000 free and free-to-try software
programs for Windows, Mac OS and Linux, games and gaming tools, Windows
device drivers, mobile devices and IT-related articles.
-----------------------------------------------------------------------
Softpedia - the encyclopedia of free software downloads
http://www.softpedia.com/

Re: [Dbfpy-users] dbfpy compatibility question

[alexander s. <al...@ty...>]

Helmut Jarausch wrote, at 26.03.2009 20:56:
> 
> 2) dbfpy stores "\0"*4 in the "Displacement of field in record"
>      (according to http://www.dbf2002.com/dbf-file-format.html)
>      whereas DBASE III+ stores   11 00 8B 3A for the
>      very first field and then   11+<sum of lengths of preceding fields>
>      for the following fields.
>      What's your rational to set this to 0?

must be a bug.  i'd expect it to be FoxPro-style offset from the 
beginning of record.

on the other hand, it does not seem to have any effect.

>      And where does this 8B 3A come from?

according to 
http://www.clicketyclick.dk/databases/xbase/format/dbf.html#DBF_NOTE_6_TARGET, 


DBASE III+ keeps in that field an "address in memory".  i have no idea 
what could be the meaning of that.

best wishes,
alex.

[Dbfpy-users] dbfpy compatibility question

[Helmut J. <jar...@sk...>]

Hi,

I've tried to modify a .dbf file for the first time.
Our good old DBASE III+ (under a DOS emulator)
didn't like this new .dbf file.

1) it has a year 2000 problem,
    it doesn't store year-1900 as dbfpy
    does, but   year % 100

2) dbfpy stores "\0"*4 in the "Displacement of field in record"
     (according to http://www.dbf2002.com/dbf-file-format.html)
     whereas DBASE III+ stores   11 00 8B 3A for the
     very first field and then   11+<sum of lengths of preceding fields>
     for the following fields.
     What's your rational to set this to 0? And where does this
     8B 3A come from?

Many thanks for your comment,
Helmut.

-- 
Helmut Jarausch

Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany