[aur-dev] dummy-data.sql
Hi, As FS#32986 isn't resolved yet, I can't test my typeahead-suggest script. Can someone please send me (off-list) a correct version of dummy-data.sql? Regards, Marcel
On Tue, Dec 11, 2012 at 1:39 PM, Marcel Korpel <marcel.lists@gmail.com> wrote:
As FS#32986 isn't resolved yet, I can't test my typeahead-suggest script. Can someone please send me (off-list) a correct version of dummy-data.sql?
On a second thought, I do have a dummy-data.sql [1], but somehow it isn't executed correctly. If I do `cat dummy-data.sql | mysql -uaur -p -v AUR` I can see the SQL commands slip by, but apparently nothing is inserted to my local database AUR, as shown by a database browser (and by the empty array my completion script returns when asking for all packages starting with 'a'). Does anyone know why this happens? Regards, Marcel [1] subset at http://pastebin.com/LukHjtwB (fully available as attachment to comment in FS#32986)
On Tue, Dec 11, 2012 at 9:17 AM, Marcel Korpel <marcel.lists@gmail.com> wrote:
On Tue, Dec 11, 2012 at 1:39 PM, Marcel Korpel <marcel.lists@gmail.com> wrote:
As FS#32986 isn't resolved yet, I can't test my typeahead-suggest script. Can someone please send me (off-list) a correct version of dummy-data.sql?
I can send one later today.
On a second thought, I do have a dummy-data.sql [1], but somehow it isn't executed correctly. If I do `cat dummy-data.sql | mysql -uaur -p -v AUR` I can see the SQL commands slip by, but apparently nothing is inserted to my local database AUR, as shown by a database browser (and by the empty array my completion script returns when asking for all packages starting with 'a').
Does anyone know why this happens?
Yes. I only fixed the problems related to character encoding of the seed file on FS#32986 so far. So some SQL dummy data will be generated from that. I didn't yet fix the character encoding of data generated from the "fortune" command for you. So gendummydata.py will stop before it prints "COMMIT;". Without that line the SQL data won't be inserted. All of these problems are avoided if you use a UTF-8 charset... Regards, Jason
On Tue, Dec 11, 2012 at 3:47 PM, canyonknight <canyonknight@gmail.com> wrote:
On Tue, Dec 11, 2012 at 9:17 AM, Marcel Korpel <marcel.lists@gmail.com> wrote:
On Tue, Dec 11, 2012 at 1:39 PM, Marcel Korpel <marcel.lists@gmail.com> wrote:
As FS#32986 isn't resolved yet, I can't test my typeahead-suggest script. Can someone please send me (off-list) a correct version of dummy-data.sql?
I can send one later today.
That would be nice.
All of these problems are avoided if you use a UTF-8 charset...
AFAIK I do use UTF-8 in my terminal, which is rxvt-unicode and font -xos4-terminus-medium-r-normal--12-120-72-72-c-60-iso10646-1. But I think you mean something else... Regards, Marcel
On Tue, Dec 11, 2012 at 05:13:50PM +0100, Marcel Korpel wrote:
On Tue, Dec 11, 2012 at 3:47 PM, canyonknight <canyonknight@gmail.com> wrote:
On Tue, Dec 11, 2012 at 9:17 AM, Marcel Korpel <marcel.lists@gmail.com> wrote:
On Tue, Dec 11, 2012 at 1:39 PM, Marcel Korpel <marcel.lists@gmail.com> wrote:
As FS#32986 isn't resolved yet, I can't test my typeahead-suggest script. Can someone please send me (off-list) a correct version of dummy-data.sql?
I can send one later today.
That would be nice.
All of these problems are avoided if you use a UTF-8 charset...
AFAIK I do use UTF-8 in my terminal, which is rxvt-unicode and font -xos4-terminus-medium-r-normal--12-120-72-72-c-60-iso10646-1. But I
That isn't UTF8, that's iso10646. Irrelevant here, though, since applications tend not to care what font your terminal uses.
think you mean something else...
Check your locale. Make sure you have a UTF-8 locale uncommented in /etc/locale.gen, that it's actually generated, and that 'locale' doesn't show any errors in displaying that LANG (well, I guess LC_CTYPE) is set to a UTF-8 locale. d
On Tue, Dec 11, 2012 at 5:27 PM, Dave Reisner <d@falconindy.com> wrote:
Check your locale. Make sure you have a UTF-8 locale uncommented in /etc/locale.gen, that it's actually generated, and that 'locale' doesn't show any errors in displaying that LANG (well, I guess LC_CTYPE) is set to a UTF-8 locale.
Ah, my LANG and all other locale variables were still set to 'C', so that caused the problem. When setting my locale to en_US.UTF-8, the file is correctly generated and the database gets populated. Only my Midnight Commander screen looks horrible, but I'll ask about that at an appropriate place. Thanks for solving this issue! Regards, Marcel
participants (3)
-
canyonknight
-
Dave Reisner
-
Marcel Korpel