Skip to main content

Directory.GetFiles - odd result

Cei mai multi dintre noi am folosit Directory.GetFiles. Aceasta metoda statica ne permite sa obtinem lista de fisere dintr-un director dat. De exemplu pentru a obtine toate fisierele din directorul 'C:\Temp' care incep cu 'Test' este nevoie sa apelam metoda GetFiles in felul urmator:
var files = Directory.GetFiles("C:\Temp","Test*");
Exemplul acesta este la mintea cocosului. Dar sa vedem ce se intampa daca vrem toate fiserele cu extensia rar.
var files = Directory.GetFiles("C:\Temp","*.rar");
In cazul in care directorul contine urmatoarele fisiere:
1.rar
2.rar
3.exe
4.rar.tmp
5.rar1
Rezultatul returnat o sa contina urmatoarele fisiere:
1.rar
2.rar
4.rar.tmp
5.rar1
Se pare ca avem o problema, ce cauta ultimele 2 fisiere in rezultat. Ne-am astepta sa fi avut ca rezultat doar 1.rar si 2.rar. Din capate in modul in care am facut noi cautarea, o sa ni se returneze orice fisere care incepe cu regula de cautare pe care noi am folosito. Rezultatul este clar nu cel asteptat.
Cauza la acest comportament este urmatoarea: metoda GetFiles() apeleaza la randul ei API de Win32 (metoda FindNextFile). Iar din cauza ca Windows-ul are atat extensii scurte de 3 caractere cat si extensi lungi (8 caractere), rezultatul returnat este cel de mai sus.
O solutie la aceasta problema este sa verificam ca rezultatul returnat se termina cu extensia pe care noi am cautato.
var files = Directory.GetFiles("C:\Temp","*.rar")
.Where( x => x.EndsWIth("*.rar");

Comments

  1. Nice :) Sau altfel spus, traiasca backward compatiblity-ul (cu FAT-ul pe 16 biti..) :)

    ReplyDelete
  2. Pe MSDN e documentata chestia asta in detaliu din cate vad, desi e clar neintuitiva...

    ReplyDelete
  3. Mie mi-a scapat, atat mie cat si unui coleg. :)

    ReplyDelete
    Replies
    1. http://msdn.microsoft.com/en-us/library/wz42302f.aspx ;)
      "When using the asterisk wildcard character in a searchPattern, such as "*.txt", the matching behavior when the extension is exactly three characters long is different than when the extension is more or less than three characters long ..."

      Delete
    2. Multumesc. Am trecut peste textul asta dar nu mi-a sarit in ochi. Eu in locul lor as fi da si un exemplu dupa fraza asta.
      Weekend placut Tudor :)

      Delete

Post a Comment

Popular posts from this blog

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...